From: Tom Lane <tgl@sss.pgh.pa.us>
To: vaclav.pink@tietoevry.com
Cc: pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #17906: Segmentation fault and database crash during procedure call
Date: Fri, 21 Apr 2023 10:09:00 -0400
Message-ID: <3337005.1682086140@sss.pgh.pa.us> (raw)
In-Reply-To: <17906-fefd777fbd04daa5@postgresql.org>
References: <17906-fefd777fbd04daa5@postgresql.org>
PG Bug reporting form <noreply@postgresql.org> writes:
> we are fighting more than 3 weeks with error: server process (PID 10028) was
> terminated by signal 11: Segmentation fault
> This error occur when I call db procedure (whole procedure is below).
Can't help you with such an incomplete bug report. If you could reduce
the problem to a self-contained test case, we'd be happy to look at it.
See
https://wiki.postgresql.org/wiki/Guide_to_reporting_problems
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 using the --to and --cc options:
reply via email
To: pgsql-bugs@postgresql.org
Cc: tgl@sss.pgh.pa.us, vaclav.pink@tietoevry.com, pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #17906: Segmentation fault and database crash during procedure call
In-Reply-To: <3337005.1682086140@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