> For the complete documentation index, see [llms.txt](https://docs.postgresql.tw/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.postgresql.tw/15/server-programming/server-programming-interface/spi-interface/spi-spi-unregister-relation.md). # SPI\_unregister\_relation ## SPI\_unregister\_relation SPI\_unregister\_relation — remove an ephemeral named relation from the registry ### Synopsis ``` int SPI_unregister_relation(const char * name) ``` ### Description `SPI_unregister_relation` removes an ephemeral named relation from the registry for the current connection. ### Arguments `const char *`` `*`name`* the relation registry entry name ### Return Value If the execution of the command was successful then the following (nonnegative) value will be returned: `SPI_OK_REL_UNREGISTER` if the tuplestore has been successfully removed from the registry On error, one of the following negative values is returned: `SPI_ERROR_ARGUMENT` if *`name`* is `NULL` `SPI_ERROR_UNCONNECTED` if called from an unconnected C function `SPI_ERROR_REL_NOT_FOUND` if *`name`* is not found in the registry for the current connection *** 原文：[PostgreSQL 15.19 Documentation](/15/server-programming/server-programming-interface/spi-interface/spi-spi-unregister-relation.md)（英文原文，待翻譯） --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.postgresql.tw/15/server-programming/server-programming-interface/spi-interface/spi-spi-unregister-relation.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.