Re: BUG #17906: Segmentation fault and database crash during procedure call - Mailing list pgsql-bugs

From Michael Paquier
Subject Re: BUG #17906: Segmentation fault and database crash during procedure call
Date
Msg-id ZE9s+lzZmVGMhbPm@paquier.xyz
Whole thread Raw
In response to Re: BUG #17906: Segmentation fault and database crash during procedure call  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses RE: BUG #17906: Segmentation fault and database crash during procedure call  (Vaclav Pink <vaclav.pink@tietoevry.com>)
List pgsql-bugs
On Fri, Apr 21, 2023 at 10:09:00AM -0400, Tom Lane wrote:
> 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

FYI, an isolated test case would require to know what's behind
the definitions of the tables apim_users, data_dictionary and domains
which are used as part of the procedure you are seeing to fail.
Likely this would require a sample of the data that fails.

Being able to get a backtrace of the crash could provide hints, though
without a data sample that may be difficult.  If you send a sample of
data, also make sure to mask anything sensitive.
--
Michael

Attachment

pgsql-bugs by date:

Previous
From: Michael Paquier
Date:
Subject: Re: BUG #17731: Server doesn't start after abnormal shutdown while creating unlogged tables
Next
From: Alexander Lakhin
Date:
Subject: Re: BUG #17912: Invalid memory access when converting plpython' array containing empty array