From: | Markus Wanner <markus(dot)wanner(at)enterprisedb(dot)com> |
---|---|
To: | Amit Kapila <amit(dot)kapila16(at)gmail(dot)com>, Ajin Cherian <itsajin(at)gmail(dot)com> |
Cc: | Markus Wanner <markus(at)bluegap(dot)ch>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
Subject: | Re: [PATCH] add concurrent_abort callback for output plugin |
Date: | 2021-03-31 06:25:36 |
Message-ID: | 8de1be1a-dde7-f50a-e47e-7e073039a127@enterprisedb.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 31.03.21 06:39, Amit Kapila wrote:
> I have slightly adjusted the comments, docs, and commit message. What
> do you think about the attached?
Thank you both, Amit and Ajin. This looks good to me.
Only one minor gripe:
> + a prepared transaction with incomplete changes, in which case the
> + <literal>concurrent_abort</literal> field of the passed
> + <literal>ReorderBufferTXN</literal> struct is set. This is done so that
> + eventually when the <command>ROLLBACK PREPARED</command> is decoded, there
> + is a corresponding prepared transaction with a matching gid.
The last sentences there now seems to relate to just the setting of
"concurrent_abort", rather than the whole reason to invoke the
prepare_cb. And the reference to the "gid" is a bit lost. Maybe:
"Thus even in case of a concurrent abort, enough information is
provided to the output plugin for it to properly deal with the
<command>ROLLBACK PREPARED</command> once that is decoded."
Alternatively, state that the gid is otherwise missing earlier in the
docs (similar to how the commit message describes it).
Regards
Markus
From | Date | Subject | |
---|---|---|---|
Next Message | Kyotaro Horiguchi | 2021-03-31 06:46:16 | Re: Issue with point_ops and NaN |
Previous Message | Julien Rouhaud | 2021-03-31 06:18:24 | Re: Idea: Avoid JOINs by using path expressions to follow FKs |