pgsql: Execute invalidation messages for each XLOG_XACT_INVALIDATIONS m

From: Amit Kapila <akapila(at)postgresql(dot)org>
To: pgsql-committers(at)lists(dot)postgresql(dot)org
Subject: pgsql: Execute invalidation messages for each XLOG_XACT_INVALIDATIONS m
Date: 2020-10-15 02:57:15
Message-ID: E1kStS7-0005eO-Aa@gemulon.postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers

Execute invalidation messages for each XLOG_XACT_INVALIDATIONS message
during logical decoding.

Prior to commit c55040ccd0 we have no way of knowing the invalidations
before commit. So, while decoding we use to execute all the invalidations
at each command end as we had no way of knowing which invalidations
happened before that command. Due to this, transactions involving large
amounts of DDLs use to take more time and also lead to high CPU usage. But
now we know specific invalidations at each command end so we execute only
required invalidations.

It has been observed that decoding of a transaction containing truncation
of a table with 1000 partitions would be finished in 1s whereas before
this patch it used to take 4-5 minutes.

Author: Dilip Kumar
Reviewed-by: Amit Kapila and Keisuke Kuroda
Discussion: https://postgr.es/m/CANDwggKYveEtXjXjqHA6RL3AKSHMsQyfRY6bK+NqhAWJyw8psQ@mail.gmail.com

Branch
------
master

Details
-------
https://git.postgresql.org/pg/commitdiff/d7eb52d7181d83cf2363570f7a205b8eb1008dbc

Modified Files
--------------
src/backend/replication/logical/reorderbuffer.c | 103 +++++++++++++++++++-----
src/include/replication/reorderbuffer.h | 12 ++-
2 files changed, 92 insertions(+), 23 deletions(-)

Browse pgsql-committers by date

  From Date Subject
Next Message Thomas Munro 2020-10-15 05:40:20 pgsql: Handle EACCES errors from kevent() better.
Previous Message Fujii Masao 2020-10-15 02:11:13 pgsql: doc: Mention that toast_tuple_target affects also column marked