| From: | Melanie Plageman <melanieplageman(at)gmail(dot)com> |
|---|---|
| To: | shihao zhong <zhong950419(at)gmail(dot)com> |
| Cc: | Rahul <rahul(at)rhyadav(dot)dev>, Kirill Reshke <reshkekirill(at)gmail(dot)com>, Nktpro <nktpro(at)gmail(dot)com>, Pgsql Bugs <pgsql-bugs(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: PostgreSQL 18.6/17.11: standby PANIC on restart after VM truncation |
| Date: | 2026-10-13 20:12:03 |
| Message-ID: | CAAKRu_Y++8RScWqKtvCQWo6ro3m=pjw-cMPG+Uho8XgR9wJBig@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
Jacky's original fix with XLogTruncateRelation() is the one I prefer.
I'm leaning toward sticking with RBM_NORMAL for heap_xlog_vm_clear()
as I don't see it halting recovery except for the truncation case, so
the natural solution to the truncation issue is to do what we do for
the main fork.
On Thu, Oct 8, 2026 at 11:13 PM shihao zhong <zhong950419(at)gmail(dot)com> wrote:
>
> The test is now 060_vm_clear_truncate.pl, on the back branches too.
> No code changes.
Attached patch uses pg_visibility to truncate and then piggy-backs on
one of its existing tests.
- Melanie
| Attachment | Content-Type | Size |
|---|---|---|
| v5-0001-Forget-invalid-VM-pages-during-truncation-replay.patch | text/x-patch | 4.7 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Sami Imseih | 2026-10-13 21:05:23 | Re: pg_stat_statements stores WITH HOLD cursor query with literals |
| Previous Message | Shlok Kyal | 2026-10-13 09:39:05 | Re: BUG #19733: Row not visible to a new snapshot after its transactional logical decoding message has been streamed |