From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
---|---|
To: | Michael Paquier <michael(at)paquier(dot)xyz> |
Cc: | "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: pgsql: Prevent tuples to be marked as dead in subtransactions on standb |
Date: | 2023-12-19 20:15:42 |
Message-ID: | CA+TgmobQNViB1E+b4njpXxcYH-ZG7f_c_yOvAautU26neY8q1w@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-committers pgsql-hackers |
On Tue, Dec 12, 2023 at 11:06 AM Michael Paquier <michael(at)paquier(dot)xyz> wrote:
> Prevent tuples to be marked as dead in subtransactions on standbys
I don't think this is a good commit message. It's totally unclear what
it means, and when I opened up the diff to try to see what was
changed, it looked nothing like what I expected.
I think a better message would have been something like
"startedInRecovery flag must be propagated to subtransactions". And I
think there should have been some analysis in the commit message or
the comments within the commit itself of whether it was intended that
this be propagated to subtransactions or not. It's hard to understand
why the flag would have been placed in the TransactionState if it
applied globally to the transaction and all subtransactions, but maybe
that's what happened.
Instead of discussing that issue, your commit message focuses in the
user-visible consequences, but in a sort of baffling way. The
statement that "Dead tuples are ignored and are not marked as dead
during recovery," for example, is clearly false on its face. If
recovery didn't mark dead tuples as dead, it would be completely
broken.
--
Robert Haas
EDB: http://www.enterprisedb.com
From | Date | Subject | |
---|---|---|---|
Next Message | Robert Haas | 2023-12-19 20:17:01 | pgsql: Fix brown paper bag bug in 5c47c6546c413d5eb51c1626070a807026e61 |
Previous Message | Tom Lane | 2023-12-19 16:12:23 | pgsql: Prevent integer overflow when forming tuple width estimates. |
From | Date | Subject | |
---|---|---|---|
Next Message | Jeff Davis | 2023-12-19 20:23:06 | Re: Change GUC hashtable to use simplehash? |
Previous Message | Robert Haas | 2023-12-19 19:22:36 | Re: backtrace_on_internal_error |