Postgres Pro
Downloads
Home   >   mailing lists

Unnecessary confirm work on logical replication - Mailing list pgsql-hackers

From Emre Hasegeli
Subject Unnecessary confirm work on logical replication
Date
Msg-id CAE2gYzwsJ_ji2CncRn1ZbCTtfvOFL5Sy=Zm2kVqAzmCFAvCSTQ@mail.gmail.com
Whole thread Raw
Responses Re: Unnecessary confirm work on logical replication  (Ashutosh Bapat <ashutosh.bapat.oss@gmail.com>)
List pgsql-hackers
Tree view 
I was reading the logical replication code and found a little
unnecessary work we are doing.

The confirmed_flushed_lsn cannot reasonably be ahead of the
current_lsn, so there is no point of calling
LogicalConfirmReceivedLocation() every time we update the candidate
xmin or restart_lsn.

Patch is attached.
Attachment

pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Fix the description of GUC "max_locks_per_transaction" and "max_pred_locks_per_transaction" in guc_table.c
Next
From: Andres Freund
Date:
Subject: Re: Minimal logical decoding on standbys