| From: | Peter Geoghegan <pg(at)bowt(dot)ie> |
|---|---|
| To: | "badfilez(at)gmail(dot)com" <badfilez(at)gmail(dot)com> |
| Cc: | pgsql-bugs(at)lists(dot)postgresql(dot)org |
| Subject: | Re: PG17.6 wal apply bug (SIGSEGV) |
| Date: | 2025-10-20 17:18:12 |
| Message-ID: | CAH2-WzmMFscVSZ5aU2t22WnD+bSU_g7ayZuGGu8SO2PJPAHahg@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
On Mon, Oct 20, 2025 at 1:07 PM badfilez(at)gmail(dot)com <badfilez(at)gmail(dot)com> wrote:
> Program terminated with signal SIGSEGV, Segmentation fault.
> #0 0x000000000057eff2 in _bt_restore_page (page=0x7f6f48fd1000 "", from=0x7f6fe2eccd80 "", len=<optimized out>) at nbtxlog.c:63
> 63 itemsz = MAXALIGN(itemsz);
> (gdb) bt full
"itemsz = 0" suggests that the index was already corrupt, before the
WAL record is applied.
I suggest that you use contrib/amcheck (or the pg_amcheck frontend
program) to ascertain the extent of any index corruption on this
database.
--
Peter Geoghegan
| From | Date | Subject | |
|---|---|---|---|
| Next Message | David Rowley | 2025-10-20 19:09:30 | Re: Potential "AIO / io workers" inter-worker locking issue in PG18? |
| Previous Message | badfilez@gmail.com | 2025-10-20 16:34:14 | Re: PG17.6 wal apply bug (SIGSEGV) |