| From: | Zhijie Hou <houzhijie22(at)gmail(dot)com> |
|---|---|
| To: | Osama Abdul Qader <osamaabdulqaderpostgres(at)gmail(dot)com> |
| Cc: | Andres Freund <andres(at)anarazel(dot)de>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>, Amit Kapila <amit(dot)kapila16(at)gmail(dot)com> |
| Subject: | Re: Avoid using raw xmin of frozen tuples in logicalrep conflict detection |
| Date: | 2026-11-08 06:10:23 |
| Message-ID: | CAFvd2n-xZ5=6yWFGxHkiRCa7jFoChabaL3k7znfpmS3JPKA2kg@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Hi,
On Sun, Nov 8, 2026 at 12:29 AM Osama Abdul Qader wrote:
>
> One possible approach for master would be to extend TupleTableSlotOps with
> a callback such as:
>
> `TransactionId (*get_effective_xmin) (TupleTableSlot *slot);`
...
> What do you think about introducing get_effective_xmin as a slot operation
> for master?
I'm afraid I find your reply quite confusing, as it is repeating the proposal
I already made in my reply to Andres, without any difference I can see.
Could you please read the discussion in this thread carefully and
share your thoughts after considering it? If you're using AI to help
draft replies, please review and understand the output fully before sending it.
--
Best Regards,
Zhijie Hou
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andrey M. Borodin | 2026-11-08 06:58:13 | Re: PoC: Simplify recovery after dropping a table by LOGGING the restore LSN |
| Previous Message | Ritesh Kumar | 2026-11-08 05:28:09 | Re: Fix recovery conflict canceling the startup progress timeout |