pg.ddx.io pgsql-bugs@postgresql.org mailing list archive
help / color / mirror / Atom feedHelp Please!
2025-04-09 18:31 UTC Carrie Ray <rdnkprncss03@aol.com>
` Re: Help Please!
2025-04-10 11:30 UTC Daniel Gustafsson <daniel@yesql.se>
` Re: Help Please!
2025-04-10 12:34 UTC Kieran McCusker <kieran.mccusker@gmail.com>
[3+ messages in thread]
BUG #18886: identity duplicate key
2025-04-09 23:04 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18886: identity duplicate key
2025-04-10 11:13 UTC hubert depesz lubaczewski <depesz@depesz.com>
` Re: BUG #18886: identity duplicate key
2025-04-10 11:18 UTC hubert depesz lubaczewski <depesz@depesz.com>
[3+ messages in thread]
BUG #18815: Logical replication worker Segmentation fault
2025-02-17 10:52 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18815: Logical replication worker Segmentation fault
2025-02-17 16:39 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #18815: Logical replication worker Segmentation fault
2025-02-17 19:17 UTC Sergey Belyashov <sergey.belyashov@gmail.com>
` Re: BUG #18815: Logical replication worker Segmentation fault
2025-02-17 19:43 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #18815: Logical replication worker Segmentation fault
2025-02-17 20:13 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #18815: Logical replication worker Segmentation fault
2025-02-17 20:57 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #18815: Logical replication worker Segmentation fault
2025-02-17 23:37 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #18815: Logical replication worker Segmentation fault
2025-02-18 01:51 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #18815: Logical replication worker Segmentation fault
2025-02-18 06:56 UTC Sergey Belyashov <sergey.belyashov@gmail.com>
` Re: BUG #18815: Logical replication worker Segmentation fault
2025-02-18 16:54 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #18815: Logical replication worker Segmentation fault
2025-02-18 17:41 UTC Sergey Belyashov <sergey.belyashov@gmail.com>
` Re: BUG #18815: Logical replication worker Segmentation fault
2025-02-18 20:38 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #18815: Logical replication worker Segmentation fault
2025-02-18 22:24 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #18815: Logical replication worker Segmentation fault
2025-02-19 06:55 UTC Sergey Belyashov <sergey.belyashov@gmail.com>
` Re: BUG #18815: Logical replication worker Segmentation fault
2025-02-19 07:06 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #18815: Logical replication worker Segmentation fault
2025-02-19 21:55 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #18815: Logical replication worker Segmentation fault
2025-02-20 19:17 UTC Sergey Belyashov <sergey.belyashov@gmail.com>
` RE: BUG #18815: Logical replication worker Segmentation fault
2025-03-26 05:07 UTC Zhijie Hou (Fujitsu) <houzj.fnst@fujitsu.com>
` Re: BUG #18815: Logical replication worker Segmentation fault
2025-04-07 09:37 UTC Amit Kapila <amit.kapila16@gmail.com>
` RE: BUG #18815: Logical replication worker Segmentation fault
2025-04-07 09:58 UTC Zhijie Hou (Fujitsu) <houzj.fnst@fujitsu.com>
` Re: BUG #18815: Logical replication worker Segmentation fault
2025-04-08 05:59 UTC Amit Kapila <amit.kapila16@gmail.com>
` RE: BUG #18815: Logical replication worker Segmentation fault
2025-04-08 06:56 UTC Zhijie Hou (Fujitsu) <houzj.fnst@fujitsu.com>
` Re: BUG #18815: Logical replication worker Segmentation fault
2025-04-09 09:29 UTC Amit Kapila <amit.kapila16@gmail.com>
[23+ messages in thread]
BUG #18884: The CURRENT_TIMESTAMP value being returned in UTC-2.
2025-04-08 13:56 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18884: The CURRENT_TIMESTAMP value being returned in UTC-2.
2025-04-08 13:58 UTC Test Test <testtest12423@gmail.com>
` Re: BUG #18884: The CURRENT_TIMESTAMP value being returned in UTC-2.
2025-04-08 14:32 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #18884: The CURRENT_TIMESTAMP value being returned in UTC-2.
2025-04-08 14:44 UTC David G. Johnston <david.g.johnston@gmail.com>
[4+ messages in thread]
BUG #18883: Epoch issue
2025-04-08 12:00 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18883: Epoch issue
2025-04-08 12:29 UTC David G. Johnston <david.g.johnston@gmail.com>
[2+ messages in thread]
BUG #18882: Unexpected write skew at SERIALIZABLE with psycopg2.connect()
2025-04-08 07:10 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18882: Unexpected write skew at SERIALIZABLE with psycopg2.connect()
2025-04-08 11:09 UTC Thomas Munro <thomas.munro@gmail.com>
[2+ messages in thread]
Aw: Re: Re: Revoke Connect Privilege from Database not working
2025-04-07 14:27 UTC Ing. Marijo Kristo <marijo.kristo@icloud.com>
BUG #18880: Can't have a database without having postgres as a db_name and username
2025-04-06 02:20 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18880: Can't have a database without having postgres as a db_name and username
2025-04-07 07:15 UTC Daniel Westermann (DWE) <daniel.westermann@dbi-services.com>
` Re: BUG #18880: Can't have a database without having postgres as a db_name and username
2025-04-07 13:48 UTC Tom Lane <tgl@sss.pgh.pa.us>
[3+ messages in thread]
BUG #18146: Rows reappearing in Tables after Auto-Vacuum Failure in PostgreSQL on Windows
2023-10-03 17:25 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18146: Rows reappearing in Tables after Auto-Vacuum Failure in PostgreSQL on Windows
2023-10-04 07:17 UTC Laurenz Albe <laurenz.albe@cybertec.at>
` Re: BUG #18146: Rows reappearing in Tables after Auto-Vacuum Failure in PostgreSQL on Windows
2023-10-04 07:24 UTC Michael Paquier <michael@paquier.xyz>
` Re: BUG #18146: Rows reappearing in Tables after Auto-Vacuum Failure in PostgreSQL on Windows
2023-10-04 14:24 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #18146: Rows reappearing in Tables after Auto-Vacuum Failure in PostgreSQL on Windows
2023-10-04 21:12 UTC Thomas Munro <thomas.munro@gmail.com>
` Re: BUG #18146: Rows reappearing in Tables after Auto-Vacuum Failure in PostgreSQL on Windows
2023-10-04 22:38 UTC Thomas Munro <thomas.munro@gmail.com>
` Re: BUG #18146: Rows reappearing in Tables after Auto-Vacuum Failure in PostgreSQL on Windows
2023-10-04 22:44 UTC Michael Paquier <michael@paquier.xyz>
` Re: BUG #18146: Rows reappearing in Tables after Auto-Vacuum Failure in PostgreSQL on Windows
2023-10-04 23:02 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #18146: Rows reappearing in Tables after Auto-Vacuum Failure in PostgreSQL on Windows
2023-10-05 19:55 UTC Thomas Munro <thomas.munro@gmail.com>
` Re: BUG #18146: Rows reappearing in Tables after Auto-Vacuum Failure in PostgreSQL on Windows
2023-10-05 20:18 UTC Thomas Munro <thomas.munro@gmail.com>
` Re: BUG #18146: Rows reappearing in Tables after Auto-Vacuum Failure in PostgreSQL on Windows
2023-10-06 04:46 UTC Thomas Munro <thomas.munro@gmail.com>
` Re: BUG #18146: Rows reappearing in Tables after Auto-Vacuum Failure in PostgreSQL on Windows
2023-10-11 14:44 UTC Robert Haas <robertmhaas@gmail.com>
` Re: BUG #18146: Rows reappearing in Tables after Auto-Vacuum Failure in PostgreSQL on Windows
2023-10-11 16:59 UTC Robert Haas <robertmhaas@gmail.com>
` Re: BUG #18146: Rows reappearing in Tables after Auto-Vacuum Failure in PostgreSQL on Windows
2023-10-12 03:36 UTC Thomas Munro <thomas.munro@gmail.com>
` Re: BUG #18146: Rows reappearing in Tables after Auto-Vacuum Failure in PostgreSQL on Windows
2023-10-19 19:50 UTC Robert Haas <robertmhaas@gmail.com>
` Re: BUG #18146: Rows reappearing in Tables after Auto-Vacuum Failure in PostgreSQL on Windows
2023-10-20 03:16 UTC Thomas Munro <thomas.munro@gmail.com>
` Re: BUG #18146: Rows reappearing in Tables after Auto-Vacuum Failure in PostgreSQL on Windows
2023-10-20 03:38 UTC Thomas Munro <thomas.munro@gmail.com>
` Re: BUG #18146: Rows reappearing in Tables after Auto-Vacuum Failure in PostgreSQL on Windows
2023-10-20 05:17 UTC Thomas Munro <thomas.munro@gmail.com>
` Re: BUG #18146: Rows reappearing in Tables after Auto-Vacuum Failure in PostgreSQL on Windows
2023-10-23 15:06 UTC Robert Haas <robertmhaas@gmail.com>
` Re: BUG #18146: Rows reappearing in Tables after Auto-Vacuum Failure in PostgreSQL on Windows
2023-10-23 21:54 UTC Thomas Munro <thomas.munro@gmail.com>
` Re: BUG #18146: Rows reappearing in Tables after Auto-Vacuum Failure in PostgreSQL on Windows
2024-04-23 07:48 UTC Thomas Munro <thomas.munro@gmail.com>
` Re: BUG #18146: Rows reappearing in Tables after Auto-Vacuum Failure in PostgreSQL on Windows
2024-05-01 05:00 UTC Michael Paquier <michael@paquier.xyz>
` Re: BUG #18146: Rows reappearing in Tables after Auto-Vacuum Failure in PostgreSQL on Windows
2024-05-14 13:00 UTC Alexander Lakhin <exclusion@gmail.com>
` Re: BUG #18146: Rows reappearing in Tables after Auto-Vacuum Failure in PostgreSQL on Windows
2024-06-26 20:58 UTC Heikki Linnakangas <hlinnaka@iki.fi>
` Re: BUG #18146: Rows reappearing in Tables after Auto-Vacuum Failure in PostgreSQL on Windows
2024-06-26 20:59 UTC Heikki Linnakangas <hlinnaka@iki.fi>
` Re: BUG #18146: Rows reappearing in Tables after Auto-Vacuum Failure in PostgreSQL on Windows
2024-09-05 23:05 UTC Thomas Munro <thomas.munro@gmail.com>
` Re: BUG #18146: Rows reappearing in Tables after Auto-Vacuum Failure in PostgreSQL on Windows
2024-09-09 07:21 UTC Michael Paquier <michael@paquier.xyz>
` Re: BUG #18146: Rows reappearing in Tables after Auto-Vacuum Failure in PostgreSQL on Windows
2024-09-09 08:57 UTC Thomas Munro <thomas.munro@gmail.com>
` Re: BUG #18146: Rows reappearing in Tables after Auto-Vacuum Failure in PostgreSQL on Windows
2024-09-10 00:43 UTC Thomas Munro <thomas.munro@gmail.com>
` Re: BUG #18146: Rows reappearing in Tables after Auto-Vacuum Failure in PostgreSQL on Windows
2024-09-11 03:20 UTC Thomas Munro <thomas.munro@gmail.com>
` Re: BUG #18146: Rows reappearing in Tables after Auto-Vacuum Failure in PostgreSQL on Windows
2024-10-29 07:48 UTC Michael Paquier <michael@paquier.xyz>
` Re: BUG #18146: Rows reappearing in Tables after Auto-Vacuum Failure in PostgreSQL on Windows
2024-11-14 15:51 UTC Robert Haas <robertmhaas@gmail.com>
` Re: BUG #18146: Rows reappearing in Tables after Auto-Vacuum Failure in PostgreSQL on Windows
2024-12-11 13:32 UTC Thomas Munro <thomas.munro@gmail.com>
` Re: BUG #18146: Rows reappearing in Tables after Auto-Vacuum Failure in PostgreSQL on Windows
2024-12-19 15:44 UTC Robert Haas <robertmhaas@gmail.com>
` Re: BUG #18146: Rows reappearing in Tables after Auto-Vacuum Failure in PostgreSQL on Windows
2024-12-20 02:53 UTC Michael Paquier <michael@paquier.xyz>
` Re: BUG #18146: Rows reappearing in Tables after Auto-Vacuum Failure in PostgreSQL on Windows
2024-12-20 22:18 UTC Thomas Munro <thomas.munro@gmail.com>
` Re: BUG #18146: Rows reappearing in Tables after Auto-Vacuum Failure in PostgreSQL on Windows
2024-12-20 23:15 UTC Thomas Munro <thomas.munro@gmail.com>
` Re: BUG #18146: Rows reappearing in Tables after Auto-Vacuum Failure in PostgreSQL on Windows
2024-12-24 05:50 UTC Michael Paquier <michael@paquier.xyz>
` Re: BUG #18146: Rows reappearing in Tables after Auto-Vacuum Failure in PostgreSQL on Windows
2025-01-07 21:57 UTC Thomas Munro <thomas.munro@gmail.com>
` Re: BUG #18146: Rows reappearing in Tables after Auto-Vacuum Failure in PostgreSQL on Windows
2025-01-07 23:50 UTC Michael Paquier <michael@paquier.xyz>
` Re: BUG #18146: Rows reappearing in Tables after Auto-Vacuum Failure in PostgreSQL on Windows
2025-01-08 03:22 UTC Michael Paquier <michael@paquier.xyz>
` Re: BUG #18146: Rows reappearing in Tables after Auto-Vacuum Failure in PostgreSQL on Windows
2025-01-08 03:48 UTC Thomas Munro <thomas.munro@gmail.com>
` Re: BUG #18146: Rows reappearing in Tables after Auto-Vacuum Failure in PostgreSQL on Windows
2025-02-05 16:36 UTC Andres Freund <andres@anarazel.de>
` Re: BUG #18146: Rows reappearing in Tables after Auto-Vacuum Failure in PostgreSQL on Windows
2025-02-06 02:43 UTC Thomas Munro <thomas.munro@gmail.com>
` Re: BUG #18146: Rows reappearing in Tables after Auto-Vacuum Failure in PostgreSQL on Windows
2025-04-06 18:16 UTC Noah Misch <noah@leadboat.com>
[45+ messages in thread]
BUG #18878: PostgreSQL triggers Assertion Failure in Debug build
2025-04-04 19:15 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18878: PostgreSQL triggers Assertion Failure in Debug build
2025-04-05 19:07 UTC Tom Lane <tgl@sss.pgh.pa.us>
[2+ messages in thread]
BUG #18877: PostgreSQL triggers assertion failure
2025-04-04 18:48 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18877: PostgreSQL triggers assertion failure
2025-04-04 19:26 UTC Liang, Yu <yuliang@psu.edu>
` Re: BUG #18877: PostgreSQL triggers assertion failure
2025-04-04 21:26 UTC Kirill Reshke <reshkekirill@gmail.com>
` Re: BUG #18877: PostgreSQL triggers assertion failure
2025-04-05 03:54 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #18877: PostgreSQL triggers assertion failure
2025-04-05 11:47 UTC Tender Wang <tndrwang@gmail.com>
` Re: BUG #18877: PostgreSQL triggers assertion failure
2025-04-05 13:03 UTC Alvaro Herrera <alvherre@alvh.no-ip.org>
` Re: BUG #18877: PostgreSQL triggers assertion failure
2025-04-05 14:47 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #18877: PostgreSQL triggers assertion failure
2025-04-05 15:00 UTC Alvaro Herrera <alvherre@alvh.no-ip.org>
` Re: BUG #18877: PostgreSQL triggers assertion failure
2025-04-05 15:12 UTC Tom Lane <tgl@sss.pgh.pa.us>
[9+ messages in thread]
BUG #18879: PostgreSQL returns memory error.
2025-04-04 19:33 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18879: PostgreSQL returns memory error.
2025-04-04 21:32 UTC Tom Lane <tgl@sss.pgh.pa.us>
[2+ messages in thread]
BUG #18396: Assert in gistFindCorrectParent() fails on inserting large tuples into gist index
2024-03-17 07:00 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18396: Assert in gistFindCorrectParent() fails on inserting large tuples into gist index
2024-03-19 12:07 UTC Tender Wang <tndrwang@gmail.com>
` Re: BUG #18396: Assert in gistFindCorrectParent() fails on inserting large tuples into gist index
2024-03-19 14:26 UTC Heikki Linnakangas <hlinnaka@iki.fi>
` Re: BUG #18396: Assert in gistFindCorrectParent() fails on inserting large tuples into gist index
2024-03-20 05:00 UTC Alexander Lakhin <exclusion@gmail.com>
` Re: BUG #18396: Assert in gistFindCorrectParent() fails on inserting large tuples into gist index
2024-03-20 06:22 UTC Tender Wang <tndrwang@gmail.com>
` Re: BUG #18396: Assert in gistFindCorrectParent() fails on inserting large tuples into gist index
2024-03-26 12:09 UTC Tender Wang <tndrwang@gmail.com>
` Re: BUG #18396: Assert in gistFindCorrectParent() fails on inserting large tuples into gist index
2024-11-15 09:10 UTC Tender Wang <tndrwang@gmail.com>
` Re: BUG #18396: Assert in gistFindCorrectParent() fails on inserting large tuples into gist index
2025-04-04 11:04 UTC Heikki Linnakangas <hlinnaka@iki.fi>
` Re: BUG #18396: Assert in gistFindCorrectParent() fails on inserting large tuples into gist index
2025-04-04 20:00 UTC Alexander Lakhin <exclusion@gmail.com>
[9+ messages in thread]
BUG #18875: COPY BINARY tsvector FROM file leads to misaligned memory access
2025-04-02 19:00 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18875: COPY BINARY tsvector FROM file leads to misaligned memory access
2025-04-02 19:45 UTC Tom Lane <tgl@sss.pgh.pa.us>
[2+ messages in thread]
BUG #17821: Assertion failed in heap_update() due to heap pruning
2023-03-02 13:00 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #17821: Assertion failed in heap_update() due to heap pruning
2023-03-04 06:00 UTC Alexander Lakhin <exclusion@gmail.com>
` Re: BUG #17821: Assertion failed in heap_update() due to heap pruning
2023-03-04 16:48 UTC Andres Freund <andres@anarazel.de>
` Re: BUG #17821: Assertion failed in heap_update() due to heap pruning
2023-10-07 08:00 UTC Alexander Lakhin <exclusion@gmail.com>
` Re: BUG #17821: Assertion failed in heap_update() due to heap pruning
2024-04-09 12:00 UTC Alexander Lakhin <exclusion@gmail.com>
` Re: BUG #17821: Assertion failed in heap_update() due to heap pruning
2024-04-09 17:41 UTC Melanie Plageman <melanieplageman@gmail.com>
` Re: BUG #17821: Assertion failed in heap_update() due to heap pruning
2024-04-09 19:00 UTC Alexander Lakhin <exclusion@gmail.com>
` Re: BUG #17821: Assertion failed in heap_update() due to heap pruning
2024-11-13 00:26 UTC Noah Misch <noah@leadboat.com>
` Re: BUG #17821: Assertion failed in heap_update() due to heap pruning
2025-01-11 21:44 UTC Noah Misch <noah@leadboat.com>
` Re: BUG #17821: Assertion failed in heap_update() due to heap pruning
2025-01-23 02:13 UTC Noah Misch <noah@leadboat.com>
` Re: BUG #17821: Assertion failed in heap_update() due to heap pruning
2025-03-03 22:07 UTC Andres Freund <andres@anarazel.de>
` Re: BUG #17821: Assertion failed in heap_update() due to heap pruning
2025-03-04 03:34 UTC Noah Misch <noah@leadboat.com>
` Re: BUG #17821: Assertion failed in heap_update() due to heap pruning
2025-04-02 17:04 UTC Noah Misch <noah@leadboat.com>
[13+ messages in thread]
BUG #18874: CVE-2024-4317
2025-04-01 14:34 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18874: CVE-2024-4317
2025-04-01 14:43 UTC Álvaro Herrera <alvherre@alvh.no-ip.org>
[2+ messages in thread]
Summing of INTERVAL returns incorrect number of days and hours
2025-04-01 13:13 UTC Milan Novotny <xnovm149@gmail.com>
` Re: Summing of INTERVAL returns incorrect number of days and hours
2025-04-01 14:19 UTC Tom Lane <tgl@sss.pgh.pa.us>
[2+ messages in thread]
Download Issue
2025-03-31 20:01 UTC farida yasmeen <faridayasmeencse@gmail.com>
` Re: Download Issue
2025-03-31 21:01 UTC David G. Johnston <david.g.johnston@gmail.com>
[2+ messages in thread]
PostgreSQL 17.4 bug with JSON+UUID under high load
2025-03-31 08:38 UTC Constantine Plotnikov <constantine.plotnikov@gmail.com>
PostgreSQL JDBC 42.7.5 returns an unexpected catalog name
2025-03-28 18:24 UTC Vinhson Nguyen <Vinhson.Nguyen@ca.ibm.com>
` Fwd: PostgreSQL JDBC 42.7.5 returns an unexpected catalog name
2025-03-29 16:21 UTC Laurenz Albe <laurenz.albe@cybertec.at>
` Re: PostgreSQL JDBC 42.7.5 returns an unexpected catalog name
2025-03-29 18:53 UTC Andrew Dunstan <andrew@dunslane.net>
[3+ messages in thread]
BUG #18871: Cross-partition MERGE fails with unclear internal error
2025-03-28 05:00 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18871: Cross-partition MERGE fails with unclear internal error
2025-03-28 16:39 UTC Tender Wang <tndrwang@gmail.com>
` Re: BUG #18871: Cross-partition MERGE fails with unclear internal error
2025-03-28 18:29 UTC Dean Rasheed <dean.a.rasheed@gmail.com>
` Re: BUG #18871: Cross-partition MERGE fails with unclear internal error
2025-03-29 02:39 UTC Tender Wang <tndrwang@gmail.com>
` Re: BUG #18871: Cross-partition MERGE fails with unclear internal error
2025-03-29 05:54 UTC Gurjeet Singh <gurjeet@singh.im>
` Re: BUG #18871: Cross-partition MERGE fails with unclear internal error
2025-03-29 10:20 UTC Dean Rasheed <dean.a.rasheed@gmail.com>
` Re: BUG #18871: Cross-partition MERGE fails with unclear internal error
2025-03-29 10:40 UTC Tender Wang <tndrwang@gmail.com>
[7+ messages in thread]
BUG #18832: Segfault in GrantLockLocal
2025-03-06 01:16 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18832: Segfault in GrantLockLocal
2025-03-07 00:49 UTC Richard Guo <guofenglinux@gmail.com>
` Re: BUG #18832: Segfault in GrantLockLocal
2025-03-07 10:37 UTC Álvaro Herrera <alvherre@alvh.no-ip.org>
` Re: BUG #18832: Segfault in GrantLockLocal
2025-03-27 09:42 UTC Robins Tharakan <tharakan@gmail.com>
` Re: BUG #18832: Segfault in GrantLockLocal
2025-03-28 06:00 UTC Alexander Lakhin <exclusion@gmail.com>
[5+ messages in thread]
BUG #18866: Running pg_freespace() on views triggers an Abort
2025-03-25 14:26 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18866: Running pg_freespace() on views triggers an Abort
2025-03-25 15:45 UTC Tender Wang <tndrwang@gmail.com>
` Re: BUG #18866: Running pg_freespace() on views triggers an Abort
2025-03-25 16:37 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #18866: Running pg_freespace() on views triggers an Abort
2025-03-26 01:18 UTC Tender Wang <tndrwang@gmail.com>
` Re: BUG #18866: Running pg_freespace() on views triggers an Abort
2025-03-26 01:55 UTC Euler Taveira <euler@eulerto.com>
` Re: BUG #18866: Running pg_freespace() on views triggers an Abort
2025-03-26 16:00 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #18866: Running pg_freespace() on views triggers an Abort
2025-03-26 16:51 UTC Euler Taveira <euler@eulerto.com>
` Re: BUG #18866: Running pg_freespace() on views triggers an Abort
2025-03-26 17:33 UTC Álvaro Herrera <alvherre@alvh.no-ip.org>
` Re: BUG #18866: Running pg_freespace() on views triggers an Abort
2025-03-26 19:00 UTC Euler Taveira <euler@eulerto.com>
` Re: BUG #18866: Running pg_freespace() on views triggers an Abort
2025-03-26 19:06 UTC Alvaro Herrera <alvherre@alvh.no-ip.org>
` Re: BUG #18866: Running pg_freespace() on views triggers an Abort
2025-03-27 07:14 UTC Tender Wang <tndrwang@gmail.com>
` Re: BUG #18866: Running pg_freespace() on views triggers an Abort
2025-03-27 08:48 UTC Richard Guo <guofenglinux@gmail.com>
` Re: BUG #18866: Running pg_freespace() on views triggers an Abort
2025-03-27 16:01 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #18866: Running pg_freespace() on views triggers an Abort
2025-03-28 01:59 UTC Tender Wang <tndrwang@gmail.com>
[14+ messages in thread]
BUG #18856: Include directives for postgresql.conf, pg_hba.conf, pg_ident.conf behave inconsistently.
2025-03-18 22:30 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18856: Include directives for postgresql.conf, pg_hba.conf, pg_ident.conf behave inconsistently.
2025-03-18 22:38 UTC Robert Pufky <rpufky@gmail.com>
` Re: BUG #18856: Include directives for postgresql.conf, pg_hba.conf, pg_ident.conf behave inconsistently.
2025-03-28 01:24 UTC Michael Paquier <michael@paquier.xyz>
[3+ messages in thread]
BUG #18845: DEREF_OF_NULL.RET guc_malloc possibly returns NULL
2025-03-14 07:58 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18845: DEREF_OF_NULL.RET guc_malloc possibly returns NULL
2025-03-14 13:50 UTC Daniel Gustafsson <daniel@yesql.se>
` Re: BUG #18845: DEREF_OF_NULL.RET guc_malloc possibly returns NULL
2025-03-14 14:04 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #18845: DEREF_OF_NULL.RET guc_malloc possibly returns NULL
2025-03-14 14:08 UTC Daniel Gustafsson <daniel@yesql.se>
` Re: BUG #18845: DEREF_OF_NULL.RET guc_malloc possibly returns NULL
2025-03-14 22:10 UTC Daniel Gustafsson <daniel@yesql.se>
` Re: BUG #18845: DEREF_OF_NULL.RET guc_malloc possibly returns NULL
2025-03-15 17:22 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #18845: DEREF_OF_NULL.RET guc_malloc possibly returns NULL
2025-03-16 19:59 UTC Daniel Gustafsson <daniel@yesql.se>
` Re: BUG #18845: DEREF_OF_NULL.RET guc_malloc possibly returns NULL
2025-03-16 20:49 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #18845: DEREF_OF_NULL.RET guc_malloc possibly returns NULL
2025-03-17 08:26 UTC Daniel Gustafsson <daniel@yesql.se>
` Re: BUG #18845: DEREF_OF_NULL.RET guc_malloc possibly returns NULL
2025-03-27 22:49 UTC Daniel Gustafsson <daniel@yesql.se>
[10+ messages in thread]
[next (older)]
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