Re: Segmentation fault - PostgreSQL 17.0
Peter Geoghegan <pg@bowt.ie>
From: Peter Geoghegan <pg@bowt.ie>
To: Tomas Vondra <tomas@vondra.me>
Cc: Ľuboslav Špilák <lspilak@microstep-hdo.sk>, "pgsql-bugs@lists.postgresql.org" <pgsql-bugs@lists.postgresql.org>
Date: 2024-11-09T15:53:39Z
Lists: pgsql-bugs
On Sat, Nov 9, 2024 at 7:01 AM Tomas Vondra <tomas@vondra.me> wrote: > Considering you're able to trigger the issue easily, it shouldn't be too > difficult to attach GDB to a backend before running the query. > Alternatively, you can enable core files, and generate the backtrace > from that. This query involves the use of a pageinspect function that accepts a raw page image. There are some sanity checks of the page, but those are quite lightweight. It's really not that hard to imagine it segfaulting from a page image that passes those checks by mistake, but is nevertheless not a valid BRIN page. In any case this should be easy to debug: save the page image that the function segfaults on, verify that it doesn't contain confidential information, and then post it here. See: https://wiki.postgresql.org/wiki/Getting_a_stack_trace_of_a_running_PostgreSQL_backend_on_Linux/BSD#contrib.2Fpageinspect_page_dump -- Peter Geoghegan
Commits
-
Detect version mismatch in brin_page_items
- 3668c1d506bf 17.3 landed
- 957ba9ff1406 18.0 landed