pgsql: Logical decoding of sequences - Mailing list pgsql-committers
From | Tomas Vondra |
---|---|
Subject | pgsql: Logical decoding of sequences |
Date | |
Msg-id | [email protected] Whole thread Raw |
List | pgsql-committers |
Logical decoding of sequences This extends the logical decoding to also decode sequence increments. We differentiate between sequences created in the current (in-progress) transaction, and sequences created earlier. This mixed behavior is necessary because while sequences are not transactional (increments are not subject to ROLLBACK), relfilenode changes are. So we do this: * Changes for sequences created in the same top-level transaction are treated as transactional, i.e. just like any other change from that transaction, and discarded in case of a rollback. * Changes for sequences created earlier are applied immediately, as if performed outside any transaction. This applies also after ALTER SEQUENCE, which may create a new relfilenode. Moreover, if we ever get support for DDL replication, the sequence won't exist until the transaction gets applied. Sequences created in the current transaction are tracked in a simple hash table, identified by a relfilenode. That means a sequence may already exist, but if a transaction does ALTER SEQUENCE then the increments for the new relfilenode will be treated as transactional. For each relfilenode we track the XID of (sub)transaction that created it, which is needed for cleanup at transaction end. We don't need to check the XID to decide if an increment is transactional - if we find a match in the hash table, it has to be the same transaction. This requires two minor changes to WAL-logging. Firstly, we need to ensure the sequence record has a valid XID - until now the the increment might have XID 0 if it was the first change in a subxact. But the sequence might have been created in the same top-level transaction. So we ensure the XID is assigned when WAL-logging increments. The other change is addition of "created" flag, marking increments for newly created relfilenodes. This makes it easier to maintain the hash table of sequences that need transactional handling. Note: This is needed because of subxacts. A XID 0 might still have the sequence created in a different subxact of the same top-level xact. This does not include any changes to test_decoding and/or the built-in replication - those will be committed in separate patches. A patch adding decoding of sequences was originally submitted by Cary Huang. This commit reworks various important aspects (e.g. the WAL logging and transactional/non-transactional handling). However, the original patch and reviews were very useful. Author: Tomas Vondra, Cary Huang Reviewed-by: Peter Eisentraut, Hannu Krosing, Andres Freund Discussion: https://postgr.es/m/[email protected] Discussion: https://postgr.es/m/[email protected] Branch ------ master Details ------- https://git.postgresql.org/pg/commitdiff/0da92dc530c9251735fc70b20cd004d9630a1266 Modified Files -------------- doc/src/sgml/logicaldecoding.sgml | 65 +++- src/backend/commands/sequence.c | 32 ++ src/backend/replication/logical/decode.c | 129 ++++++++ src/backend/replication/logical/logical.c | 88 +++++ src/backend/replication/logical/reorderbuffer.c | 405 ++++++++++++++++++++++++ src/include/access/rmgrlist.h | 2 +- src/include/commands/sequence.h | 1 + src/include/replication/decode.h | 1 + src/include/replication/output_plugin.h | 27 ++ src/include/replication/reorderbuffer.h | 43 ++- 10 files changed, 786 insertions(+), 7 deletions(-)
pgsql-committers by date: