Re: Segmentation fault - PostgreSQL 17.0 - Mailing list pgsql-bugs

From Peter Geoghegan
Subject Re: Segmentation fault - PostgreSQL 17.0
Date
Msg-id CAH2-Wz=fNAq4f5=aAyixxDviD5qLPL2Y_wsay6mOUeNFCeKFnQ@mail.gmail.com
Whole thread Raw
In response to Re: Segmentation fault - PostgreSQL 17.0  (Tomas Vondra <tomas@vondra.me>)
List 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



pgsql-bugs by date:

Previous
From: Ľuboslav Špilák
Date:
Subject: Re: Segmentation fault - PostgreSQL 17.0
Next
From: Tomas Vondra
Date:
Subject: Re: Segmentation fault - PostgreSQL 17.0