Re-add SPICleanup for ABI compatibility in stable branch

This fixes an ABI break introduced by
2f6b8c287b881fd33168d8c15c56f71163ff3ba6.

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 94bcb48ab5
commit 6d61aef5db
2 changed files with 11 additions and 0 deletions

View File

@ -381,6 +381,16 @@ SPI_rollback(void)
PG_END_TRY();
}
/*
* 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

@ -163,6 +163,7 @@ extern void SPI_start_transaction(void);
extern void SPI_commit(void);
extern void SPI_rollback(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);