causing crash - Search results in mailing lists
Mailing lists >> pgsql-bugs >> Thread
2025-04-12 06:34:59 | BUG #18893: Segfault during analyze pg_database (PG Bug reporting form)
causes a segfault. Tested on a recent - 847bbb21f8c4eb0e2b47417684ad2ba9255c9e80. Backtrace below but to add, every time I stepped on this, postgres was always analyzing pg_database. Repro (a few runs may be required
Mailing lists >> pgsql-bugs >> Thread
2025-03-31 11:38:37 | PostgreSQL 17.4 bug with JSON+UUID under high load (Constantine Plotnikov)
crashed. The sample code that reproduces the problem is at https:///const/pg-json-uuid-bug. The README.adoc at the root contains a detailed description. The bug was originally detected in official docker image postgres
Mailing lists >> pgsql-bugs >> Thread
2025-03-13 02:37:33 | Re: BUG #18840: Segmentation fault in executing select unnest(array(oidvector)) (Tom Lane)
causes visibly bogus answers in some cases but gives seemingly-sane results in others; I have not found a case where it'd crash
Mailing lists >> pgsql-bugs >> Thread
2025-03-06 04:16:57 | BUG #18832: Segfault in GrantLockLocal (PG Bug reporting form)
cause, but what I can add is that I've run similar workloads last month and these crashes
Mailing lists >> pgsql-bugs >> Thread >> Search in thread (3)
2025-03-04 14:32:12 | Re: BUG #18830: ExecInitMerge Segfault on MERGE (Amit Langote)
causing the crash Robins reported. If there's a separate bug, we have to check
Mailing lists >> pgsql-bugs >> Thread
2025-02-17 19:39:11 | Re: BUG #18815: Logical replication worker Segmentation fault (Tom Lane)
cause the failure. Something that might be less work for you is to get a stack trace from the crash
Mailing lists >> pgsql-bugs >> Thread
2025-02-13 17:57:14 | Re: BUG #18810: invalid value for parameter "synchronized_standby_slots" Caused error:"Segmentation fault" (Tom Lane)
PG Bug reporting form
Mailing lists >> pgsql-bugs >> Thread >> Search in thread (2)
2025-02-12 21:12:20 | Re: BRIN index creation on geometry column causes crash (Tomas Vondra)
On 2/12/25 11:55, Álvaro Herrera wrote: Yeah, I'm not opposed to doing this
Mailing lists >> pgsql-bugs >> Thread
2025-02-05 10:38:47 | BUG #18795: Norwegian bokmål crashes again (PG Bug reporting form)
The following bug has been logged on the website: Bug reference: 18795 Logged by: Øystein
Mailing lists >> pgsql-bugs >> Thread
2025-01-03 03:15:06 | Re: BRIN index creation on geometry column causes crash (David Rowley)
On Fri, 3 Jan 2025 at 11:02, Tobias Wendorff
Mailing lists >> pgsql-bugs >> Thread
2024-12-10 20:54:22 | Re: pg_dump crash on identity sequence with not loaded attributes (Artur Zakirov)
dumpSequence() and which causes the crash. Are there any downsides of it? -- Kind regards, Artur
Mailing lists >> pgsql-bugs >> Thread
2024-12-05 04:04:16 | Tablespace storage bug... (Greg Kemnitz)
caused a load of a six billion row table to crash as the / partition unexpectedly
Mailing lists >> pgsql-bugs >> Thread
2024-11-09 19:35:05 | Re: Segmentation fault - PostgreSQL 17.0 (Ľuboslav Špilák)
caused sigsegv again.
Thank you.
Best regards,
Lubo
________________________________
From: Tomas Vondra
Mailing lists >> pgsql-bugs >> Thread >> Search in thread (2)
2024-10-17 03:56:52 | Re: BUG #18657: Using JSON_OBJECTAGG with volatile function leads to segfault (Tom Lane)
cause EXPLAIN to crash or at least produce wrong results. In other words, the proposed
Mailing lists >> pgsql-bugs >> Thread
2024-10-06 21:08:25 | Re: Server crash when selecting from pg_cursors (Tom Lane)
PetSerAl