If you find a bug, please use the bug reporting form.
Thread | Author | Time |
---|---|---|
Self referential foreign keys in partitioned table not working as expected | Luca Vallisa | 09:06 |
Re: Self referential foreign keys in partitioned table not working as expected | Christoph Berg | 10:18 |
Re: Self referential foreign keys in partitioned table not working as expected | Luca Vallisa | 10:24 |
Re: Self referential foreign keys in partitioned table not working as expected | Christoph Berg | 10:46 |
Summing of INTERVAL returns incorrect number of days and hours | Milan Novotny | 13:13 |
Re: Summing of INTERVAL returns incorrect number of days and hours | Tom Lane | 14:19 |
BUG #18874: CVE-2024-4317 | PG Bug reporting form | 14:34 |
Re: BUG #18874: CVE-2024-4317 | Álvaro Herrera | 14:43 |
Thread | Author | Time |
---|---|---|
Re: BUG #17821: Assertion failed in heap_update() due to heap pruning 📎 | Noah Misch | 17:04 |
BUG #18875: COPY BINARY tsvector FROM file leads to misaligned memory access | PG Bug reporting form | 19:00 |
Re: BUG #18875: COPY BINARY tsvector FROM file leads to misaligned memory access | Tom Lane | 19:45 |
Thread | Author | Time |
---|---|---|
BUG #18876: HINT messages for mxid wrap-around say "drop stale slots", but that may not be appropriate | PG Bug reporting form | 03:05 |
Re: BUG #18396: Assert in gistFindCorrectParent() fails on inserting large tuples into gist index | Heikki Linnakangas | 11:04 |
Re: PostgreSQL v15.12 fails to perform PG_UPGRADE from v13 and v9 on Windows | Manika Singhal | 12:30 |
BUG #18877: PostgreSQL triggers assertion failure | PG Bug reporting form | 18:48 |
BUG #18878: PostgreSQL triggers Assertion Failure in Debug build | PG Bug reporting form | 19:15 |
Re: BUG #18877: PostgreSQL triggers assertion failure | Liang, Yu | 19:26 |
BUG #18879: PostgreSQL returns memory error. | PG Bug reporting form | 19:33 |
Re: BUG #18396: Assert in gistFindCorrectParent() fails on inserting large tuples into gist index | Alexander Lakhin | 20:00 |
Re: BUG #18877: PostgreSQL triggers assertion failure | Kirill Reshke | 21:26 |
Re: BUG #18879: PostgreSQL returns memory error. | Tom Lane | 21:32 |
Thread | Author | Time |
---|---|---|
Re: BUG #18877: PostgreSQL triggers assertion failure | Tom Lane | 03:54 |
Re: BUG #18877: PostgreSQL triggers assertion failure | Tender Wang | 11:47 |
Re: BUG #18877: PostgreSQL triggers assertion failure 📎 | Alvaro Herrera | 13:03 |
Re: BUG #18877: PostgreSQL triggers assertion failure | Tom Lane | 14:47 |
Re: BUG #18877: PostgreSQL triggers assertion failure | Alvaro Herrera | 15:00 |
Re: BUG #18877: PostgreSQL triggers assertion failure | Tom Lane | 15:12 |
Re: BUG #18878: PostgreSQL triggers Assertion Failure in Debug build | Tom Lane | 19:07 |
Thread | Author | Time |
---|---|---|
BUG #18880: Can't have a database without having postgres as a db_name and username | PG Bug reporting form | 02:20 |
Re: BUG #18146: Rows reappearing in Tables after Auto-Vacuum Failure in PostgreSQL on Windows | Noah Misch | 18:16 |
Thread | Author | Time |
---|---|---|
Re: BUG #18880: Can't have a database without having postgres as a db_name and username | Daniel Westermann (DWE) | 07:15 |
Re: BUG #18815: Logical replication worker Segmentation fault | Amit Kapila | 09:37 |
RE: BUG #18815: Logical replication worker Segmentation fault | Zhijie Hou (Fujitsu) | 09:58 |
Re: Re: Revoke Connect Privilege from Database not working | David G. Johnston | 13:42 |
Re: BUG #18880: Can't have a database without having postgres as a db_name and username | Tom Lane | 13:48 |
Aw: Re: Re: Revoke Connect Privilege from Database not working | Ing. Marijo Kristo | 14:27 |
Re: PostgreSQL v15.12 fails to perform PG_UPGRADE from v13 and v9 on Windows | Avi Uziel | 14:59 |
Re: Re: Re: Revoke Connect Privilege from Database not working | David G. Johnston | 15:37 |
Re: Re: Re: Revoke Connect Privilege from Database not working | Tom Lane | 16:06 |
Re: Re: Re: Revoke Connect Privilege from Database not working | David G. Johnston | 16:22 |
Thread | Author | Time |
---|---|---|
Re: ERROR: tuple to be updated was already modified by an operation triggered by the current command | Robins Tharakan | 12:48 |
Re: ERROR: tuple to be updated was already modified by an operation triggered by the current command | Noah Misch | 14:41 |
Re: BUG #18885: ERROR: corrupt MVNDistinct entry - 2 | Alexander Korotkov | 22:30 |
Re: BUG #18831: Particular queries using gin-indexes are not interruptible, resulting is resource usage concerns. 📎 | Vinod Sridharan | 23:38 |
Re: BUG #18831: Particular queries using gin-indexes are not interruptible, resulting is resource usage concerns. | Tom Lane | 23:54 |
Thread | Author | Time |
---|---|---|
Re: BUG #18893: Segfault during analyze pg_database | Robins Tharakan | 12:11 |
Re: BUG #18892: When the view already exists, CREATE OR REPLACE VIEW does not check whether the table exists. | Kirill Reshke | 13:09 |
Re: BUG #18892: When the view already exists, CREATE OR REPLACE VIEW does not check whether the table exists. | Tom Lane | 14:05 |
Re: BUG #18893: Segfault during analyze pg_database | Tom Lane | 14:13 |
Re: BUG #18885: ERROR: corrupt MVNDistinct entry - 2 📎 | David Rowley | 23:26 |
Thread | Author | Time |
---|---|---|
BUG #18894: values of JLC_COLLATE and LC_CTYPE in the database have changed from Japanese_Japan.932 to ja-jp | PG Bug reporting form | 06:08 |
回复: BUG #18892: When the view already exists, CREATE OR REPLACE VIEW does not check whether the table exists. | Gang Chen | 08:55 |
Re: BUG #18893: Segfault during analyze pg_database | Robins Tharakan | 09:18 |
Missing whitespace in pg_restore manpage | Lele Gaifax | 09:55 |
Re: BUG #18885: ERROR: corrupt MVNDistinct entry - 2 📎 | Andrei Lepikhov | 14:41 |
Re: BUG #18894: values of JLC_COLLATE and LC_CTYPE in the database have changed from Japanese_Japan.932 to ja-jp | Laurenz Albe | 17:30 |
Thread | Author | Time |
---|---|---|
Re: Missing whitespace in pg_restore manpage 📎 | Fujii Masao | 05:47 |
Re: Missing whitespace in pg_restore manpage | Lele Gaifax | 05:56 |
Re: BUG #18885: ERROR: corrupt MVNDistinct entry - 2 | Andrei Lepikhov | 09:41 |
Re: BUG #18885: ERROR: corrupt MVNDistinct entry - 2 | Tomas Vondra | 13:16 |
Re: Missing whitespace in pg_restore manpage | Fujii Masao | 14:19 |
Re: BUG #18894: values of JLC_COLLATE and LC_CTYPE in the database have changed from Japanese_Japan.932 to ja-jp | Manika Singhal | 14:46 |
Re: PostgreSQL v15.12 fails to perform PG_UPGRADE from v13 and v9 on Windows | Manika Singhal | 14:51 |
Re: PostgreSQL v15.12 fails to perform PG_UPGRADE from v13 and v9 on Windows | Nico Williams | 16:10 |
Re: PostgreSQL v15.12 fails to perform PG_UPGRADE from v13 and v9 on Windows | Thomas Munro | 21:11 |
Re: PostgreSQL v15.12 fails to perform PG_UPGRADE from v13 and v9 on Windows | Nico Williams | 21:33 |
Thread | Author | Time |
---|---|---|
BUG #18898: replication process not working... sometimes | PG Bug reporting form | 00:09 |
pg_restore error with partitioned table having exclude constraint | Keith Paskett | 05:11 |
Re: pg_restore error with partitioned table having exclude constraint 📎 | Japin Li | 11:06 |
Re: pg_restore error with partitioned table having exclude constraint | Álvaro Herrera | 13:06 |
Re: pg_restore error with partitioned table having exclude constraint | Japin Li | 14:54 |
Re: pg_restore error with partitioned table having exclude constraint | Álvaro Herrera | 15:18 |
Re: pg_restore error with partitioned table having exclude constraint | Keith Paskett | 19:03 |
Re: PostgreSQL v15.12 fails to perform PG_UPGRADE from v13 and v9 on Windows | Nico Williams | 19:18 |
Re: PostgreSQL v15.12 fails to perform PG_UPGRADE from v13 and v9 on Windows | Nico Williams | 19:31 |
Thread | Author | Time |
---|---|---|
RE: BUG #18898: replication process not working... sometimes 📎 | Hayato Kuroda (Fujitsu) | 12:31 |
BUG #18899: FreeBSD, assembly by means of GCC with ASAN ends with error: undef reference to backtrace_symbols_fd | PG Bug reporting form | 12:38 |
Re: BUG #18899: FreeBSD, assembly by means of GCC with ASAN ends with error: undef reference to backtrace_symbols_fd | Tom Lane | 17:38 |
Disabled logical replication origin session causes primary key errors 📎 | Shawn McCoy | 21:22 |
Thread | Author | Time |
---|---|---|
Re: BUG #18896: A potential problem in heap_page_items (pageinspect, PG-17) | Tom Lane | 19:33 |
Thread | Author | Time |
---|---|---|
Re: Disabled logical replication origin session causes primary key errors | Masahiko Sawada | 05:53 |
Re: Error when using array_agg with filter where clause in pg16 and pg17 | David Rowley | 10:21 |
Thread | Author | Time |
---|---|---|
Re: Disabled logical replication origin session causes primary key errors | Michael Paquier | 02:25 |
Re: BUG #18897: Logical replication conflict after using pg_createsubscriber under heavy load | vignesh C | 03:38 |