| From: | Bertrand Drouvot <bertranddrouvot(dot)pg(at)gmail(dot)com> |
|---|---|
| To: | Masahiko Sawada <sawada(dot)mshk(at)gmail(dot)com> |
| Cc: | Amit Kapila <amit(dot)kapila16(at)gmail(dot)com>, Zhijie Hou <houzhijie22(at)gmail(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Assertion failure in update_local_synced_slot(), slotsync.c:364 |
| Date: | 2026-11-16 07:51:55 |
| Message-ID: | avq2GwxZ5uJSLV08@bdtpg |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Hi,
On Sun, Nov 15, 2026 at 10:35:57PM -0800, Masahiko Sawada wrote:
>
> I'm concerned that not only changes to this function but also changes
> to its callers could break these assumptions, and nothing near those
> places would tell us about them.
Yeah, I agree with this concern. Looking at 788ec96d591, I think remote_slot_precedes
was redundant with slotsync_skip_reason, but found_consistent_snapshot was not:
slotsync_skip_reason reports why synchronization was skipped, while found_consistent_snapshot
tells the caller whether the slot is safe to persist.
v2 is correct with the current temporary slot caller, which persists the slot
immediately. But relying on this call sequence seems fragile. So I'd vote for
restoring found_consistent_snapshot.
Regards,
--
Bertrand Drouvot
PostgreSQL Contributors Team
RDS Open Source Databases
Amazon Web Services: https://aws.amazon.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Zhijie Hou | 2026-11-16 08:09:44 | Re: Assertion failure in update_local_synced_slot(), slotsync.c:364 |
| Previous Message | David Geier | 2026-11-16 07:47:33 | Re: Keep TIDBitmap pagetable memory across bitmap scans |