On 8/6/25 05:37, Charles Qi wrote:
And if we do the updates in multiple subtransactions, multixact will be
created, which is not created when the BEFORE ROW UPDATE trigger is absent.
Is this behavior by design? If so, what is the purpose for the behavior?
I would say this is by design. My reasoning is that the savepoints are
essentially rollback points and the state of the tuple would need to be
saved for each potential rollback. Hence a different transaction id for
each savepoint.
Tested version:
PostgreSQL 14.18 (Ubuntu 14.18-0ubuntu0.22.04.1) on x86_64-pc-linux-gnu,
compiled by gcc (Ubuntu 11.4.0-1ubuntu1~22.04) 11.4.0, 64-bit
The attached file reproduce.sql can be used to reproduce the behavior.
--
Adrian Klaver
adrian.klaver@xxxxxxxxxxx
