Re-add SPICleanup for ABI compatibility in stable branch

This fixes an ABI break introduced by
cfc86f987349372dbbfc0391f9f519c0a7b27b84.

Author: Markus Wanner <markus.wanner@enterprisedb.com>
Discussion: https://www.postgresql.org/message-id/defd749a-8410-841d-1126-21398686d63d@enterprisedb.com
This commit is contained in:
Peter Eisentraut 2022-07-18 16:23:48 +02:00
parent 36ccca3dba
commit b2c8d56618
2 changed files with 11 additions and 0 deletions

View File

@ -416,6 +416,16 @@ SPI_rollback_and_chain(void)
_SPI_rollback(true);
}
/*
* SPICleanup is a no-op, kept for backwards compatibility. We rely on
* AtEOXact_SPI to cleanup. Extensions should not (need to) fiddle with the
* internal SPI state directly.
*/
void
SPICleanup(void)
{
}
/*
* Clean up SPI state at transaction commit or abort.
*/

View File

@ -167,6 +167,7 @@ extern void SPI_commit_and_chain(void);
extern void SPI_rollback(void);
extern void SPI_rollback_and_chain(void);
extern void SPICleanup(void);
extern void AtEOXact_SPI(bool isCommit);
extern void AtEOSubXact_SPI(bool isCommit, SubTransactionId mySubid);
extern bool SPI_inside_nonatomic_context(void);