public inbox for [email protected]  

help / color / mirror / Atom feed

From: David Rowley <[email protected]>
To: milist ujang <[email protected]>
Cc: [email protected]
Subject: Re: signal 11: Segmentation fault ; query constraint list; pg16.3
Date: Mon, 20 May 2024 23:01:05 +1200
Message-ID: <CAApHDvqL3X+1QyapTchBvLbsLHHcYXRwtGEEb7PK2kpi4tc4Nw@mail.gmail.com> (raw)
In-Reply-To: <CACG9ogyCjz6yBKBuTX=686CypkgQj+RjrtAw2Skj1Q=0AxxG3Q@mail.gmail.com>
References: <CACG9ogyCjz6yBKBuTX=686CypkgQj+RjrtAw2Skj1Q=0AxxG3Q@mail.gmail.com>

On Mon, 20 May 2024 at 22:32, milist ujang <[email protected]> wrote:
>
> postgres 16.1; rocky 9.3
>
> when connect to database postgres this query is OK, but run on user database, got segmentation fault.

I tried your query on 16.1 and I'm unable to reproduce the crash.

Are you able to recreate this on a freshly installed instance after
creating the table in question? If not, does it crash after you do a
pg_dump --schema-only from the problem database and restoring that to
the fresh instance and running ANALYZE? The crash may depend on the
query plan chosen and that will depend on the schema in that database.

We're probably going to need a recreator script for this. You might be
able to come up with one from doing the --schema-only dump and
restoring that somewhere and dropping unrelated objects to find the
minimum set you need for the crash.

Alternatively, a stack trace would be useful. See:

https://wiki.postgresql.org/wiki/Getting_a_stack_trace_of_a_running_PostgreSQL_backend_on_Linux/BSD

David

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: [email protected]
  Cc: [email protected], [email protected]
  Subject: Re: signal 11: Segmentation fault ; query constraint list; pg16.3
  In-Reply-To: <CAApHDvqL3X+1QyapTchBvLbsLHHcYXRwtGEEb7PK2kpi4tc4Nw@mail.gmail.com>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox