From: | Peter Geoghegan <pg(at)bowt(dot)ie> |
---|---|
To: | Tomas Vondra <tomas(at)vondra(dot)me> |
Cc: | Ľuboslav Špilák <lspilak(at)microstep-hdo(dot)sk>, "pgsql-bugs(at)lists(dot)postgresql(dot)org" <pgsql-bugs(at)lists(dot)postgresql(dot)org> |
Subject: | Re: Segmentation fault - PostgreSQL 17.0 |
Date: | 2024-11-09 15:53:39 |
Message-ID: | CAH2-Wz=fNAq4f5=aAyixxDviD5qLPL2Y_wsay6mOUeNFCeKFnQ@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
On Sat, Nov 9, 2024 at 7:01 AM Tomas Vondra <tomas(at)vondra(dot)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:
--
Peter Geoghegan
From | Date | Subject | |
---|---|---|---|
Next Message | Tomas Vondra | 2024-11-09 16:07:40 | Re: Segmentation fault - PostgreSQL 17.0 |
Previous Message | Ľuboslav Špilák | 2024-11-09 13:02:11 | Re: Segmentation fault - PostgreSQL 17.0 |