| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | vaclav(dot)pink(at)tietoevry(dot)com |
| Cc: | pgsql-bugs(at)lists(dot)postgresql(dot)org |
| Subject: | Re: BUG #17906: Segmentation fault and database crash during procedure call |
| Date: | 2023-04-21 14:09:00 |
| Message-ID: | 3337005.1682086140@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
PG Bug reporting form <noreply(at)postgresql(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Nathan Bossart | 2023-04-21 21:43:47 | Re: BUG #17903: There is a bug in the KeepLogSeg() |
| Previous Message | Andrey Lepikhov | 2023-04-21 12:11:04 | Re: Clause accidentally pushed down ( Possible bug in Making Vars outer-join aware) |