Hello,
SPI was originally developed for execution SQL statements from C user
defined functions in context of existed transaction.
This is why it is not possible to execute any transaction manipulation
statement (BEGIN, COMMIT, PREPARE,...) using
SPI_execute:SPI_ERROR_TRANSACTION is returned.
But now SPI is used not only inside UDFs. It is also used in background
workers. For example in receiver_raw, written by Michael Paquier (I lot
of thanks Michael, understand logical replication without them will be
much more difficult).
Right now transactions have to be started by background worker using
StartTransactionCommand().
So receiver_raw is not able to preserve master's transaction semantic
(certainly it can be implemented).
I wonder whether SPI can be extended now to support transaction
manipulation functions when been called outside transaction context? Or
there are some principle problem with it?
Thanks in advance,
Konstantin
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
