public inbox for [email protected]  

help / color / mirror / Atom feed

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

as of subject, it should be 16.3.

scenario was:
- a few months ago install + deployed user data pg 16.2.
- 2 days ago, updated to 16.3

now I can reproduce the issue, the segment fault comes from
postgres[495645]: segfault at 0 ip 00007f318b17e1f4 sp 00007ffc7f1b15d8
error 4 in citus.so[7f318b0a4000+ee000] likely on CPU 93 (core 1, socket 1)

after dropping the citus extension, now it's OK.

Thanks for the reply.


On Mon, May 20, 2024 at 6:01 PM David Rowley <[email protected]> wrote:

> 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
>


-- 
regards

ujang jaenudin | Self-Employed, DBA Consultant
http://id.linkedin.com/pub/ujang-jaenudin/12/64/bab

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]
  Subject: Re: signal 11: Segmentation fault ; query constraint list; pg16.3
  In-Reply-To: <CACG9ogw1sGqX5vc=X9922tvN7dKJnazhnyjHXtF0ppY3=G=3ZA@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