From: Tom Lane <tgl@sss.pgh.pa.us>
To: Willian Colognesi <willian_colognesi@trimble.com>
Cc: pgsql-general@lists.postgresql.org
Subject: Re: Segmentation Fault PG 14
Date: Mon, 07 Nov 2022 13:08:47 -0500
Message-ID: <3316399.1667844527@sss.pgh.pa.us> (raw)
In-Reply-To: <CADAf1kavcN-kY=vEm3MYxhUa+rtGFs7tym5d7Ee6Ni2cwwxGqQ@mail.gmail.com>
References: <CADAf1kavcN-kY=vEm3MYxhUa+rtGFs7tym5d7Ee6Ni2cwwxGqQ@mail.gmail.com>
Willian Colognesi <willian_colognesi@trimble.com> writes:
> I started to use version `14.5-2.pgdg20.04+2` for a dedicated database and
> I'm facing many segmentation faults during the day when the database has
> more heavy queries.
I take it things were okay with the version you used previously?
What was that exactly? Has anything else changed?
> I could also get a little information from gdb, I'm not sure if it will
> help:
This looks pretty messed up. Are you sure the debug symbols you're using
match the package?
Even better, can you construct a self-contained test case?
regards, tom lane
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 from your mail client; the link fills in
the headers below: reply via email
Some clients, webmail especially, drop In-Reply-To and References from
a link, and the reply then starts a new thread: use the mbox below.
To: pgsql-general@postgresql.org
Cc: tgl@sss.pgh.pa.us, willian_colognesi@trimble.com
Subject: Re: Segmentation Fault PG 14
In-Reply-To: <3316399.1667844527@sss.pgh.pa.us>
References: <CADAf1kavcN-kY=vEm3MYxhUa+rtGFs7tym5d7Ee6Ni2cwwxGqQ@mail.gmail.com> <3316399.1667844527@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox