Re: locking [user] catalog tables vs 2pc vs logical rep

vignesh C <vignesh21@gmail.com>

From: vignesh C <vignesh21@gmail.com>
To: Ajin Cherian <itsajin@gmail.com>
Cc: Andres Freund <andres@anarazel.de>, Pg Hackers <pgsql-hackers@postgresql.org>, Amit Kapila <amit.kapila16@gmail.com>, Markus Wanner <markus.wanner@enterprisedb.com>
Date: 2021-03-31T12:17:50Z
Lists: pgsql-hackers

Attachments

On Wed, Mar 31, 2021 at 2:35 PM Ajin Cherian <itsajin@gmail.com> wrote:
>
> The patch applies fine on HEAD and "make check" passes fine. No major comments on the patch, just a minor comment:
>
> If you could change the error from, " cannot PREPARE a transaction that has a lock on user catalog/system table(s)"
> to "cannot PREPARE a transaction that has an exclusive lock on user catalog/system table(s)" that would be a more
> accurate instruction to the user.
>

Thanks for reviewing the patch.
Please find the updated patch which includes the fix for the same.

Regards,
Vignesh

Commits

  1. Doc: Update caveats in synchronous logical replication.

  2. Document a few caveats in synchronous logical replication.

  3. Update the docs and comments for decoding of prepared xacts.

  4. Allow decoding at prepare time in ReorderBuffer.

  5. Documentation for logical decoding.