pgsql-bugs - April 2025

If you find a bug, please use the bug reporting form.

Search the Archives

(enter a message-id to go directly to that message)

Browse Archives

Prev | Next

April 1, 2025

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

April 2, 2025

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

April 4, 2025

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

April 5, 2025

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

April 6, 2025

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

April 7, 2025

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

April 8, 2025

Thread Author Time
Re: PostgreSQL v15.12 fails to perform PG_UPGRADE from v13 and v9 on Windows Laurenz Albe 05:50
Re: BUG #18815: Logical replication worker Segmentation fault Amit Kapila 05:59
RE: BUG #18815: Logical replication worker Segmentation fault 📎 Zhijie Hou (Fujitsu) 06:56
BUG #18882: Unexpected write skew at SERIALIZABLE with psycopg2.connect() PG Bug reporting form 07:10
Re: BUG #18882: Unexpected write skew at SERIALIZABLE with psycopg2.connect() Thomas Munro 11:09
BUG #18883: Epoch issue PG Bug reporting form 12:00
Re: BUG #18883: Epoch issue David G. Johnston 12:29
Error when using array_agg with filter where clause in pg16 and pg17 Kaimeh 12:38
BUG #18884: The CURRENT_TIMESTAMP value being returned in UTC-2. PG Bug reporting form 13:56
Re: BUG #18884: The CURRENT_TIMESTAMP value being returned in UTC-2. Test Test 13:58
Re: BUG #18884: The CURRENT_TIMESTAMP value being returned in UTC-2. Tom Lane 14:32
Re: BUG #18884: The CURRENT_TIMESTAMP value being returned in UTC-2. David G. Johnston 14:44
Re: Error when using array_agg with filter where clause in pg16 and pg17 Tom Lane 15:32
Re: Error when using array_agg with filter where clause in pg16 and pg17 📎 David Rowley 23:55

April 9, 2025

Thread Author Time
Re: Error when using array_agg with filter where clause in pg16 and pg17 Tom Lane 00:25
Re: Error when using array_agg with filter where clause in pg16 and pg17 David Rowley 00:43
Re: Error when using array_agg with filter where clause in pg16 and pg17 Tom Lane 00:52
Re: Error when using array_agg with filter where clause in pg16 and pg17 David Rowley 00:54
Re: Error when using array_agg with filter where clause in pg16 and pg17 David Rowley 01:50
Re: Error when using array_agg with filter where clause in pg16 and pg17 Tom Lane 02:36
Re: Error when using array_agg with filter where clause in pg16 and pg17 David Rowley 02:55
Re: BUG #18815: Logical replication worker Segmentation fault Amit Kapila 09:29
BUG #18885: ERROR: corrupt MVNDistinct entry - 2 PG Bug reporting form 13:46
Help Please! Carrie Ray 18:31
Re: BUG #18885: ERROR: corrupt MVNDistinct entry - 2 Tomas Vondra 22:47
BUG #18886: identity duplicate key PG Bug reporting form 23:04
Re: PostgreSQL v15.12 fails to perform PG_UPGRADE from v13 and v9 on Windows Thomas Munro 23:49

April 10, 2025

Thread Author Time
Re: PostgreSQL v15.12 fails to perform PG_UPGRADE from v13 and v9 on Windows Manika Singhal 07:02
Re: PostgreSQL v15.12 fails to perform PG_UPGRADE from v13 and v9 on Windows Thomas Munro 07:14
Re: BUG #18886: identity duplicate key hubert depesz lubaczewski 11:13
Re: BUG #18886: identity duplicate key hubert depesz lubaczewski 11:18
Re: Help Please! Daniel Gustafsson 11:30
Re: BUG #18885: ERROR: corrupt MVNDistinct entry - 2 📎 Andrei Lepikhov 12:28
Re: Help Please! Kieran McCusker 12:34
BUG #18887: Inner join returns non-existent data. PG Bug reporting form 15:50
BUG #18888: /src/interfaces/ecpg/preproc/descriptor.c possible NULL dereference PG Bug reporting form 16:39
BUG #18889: /src/backend/utils/adt/network.c condition is always false PG Bug reporting form 16:41
BUG #18890: /src/timezone/localtime.c condition always false PG Bug reporting form 16:44
BUG #18891: /src/include/lib/simplehash.h possible palloc0 problems PG Bug reporting form 16:47
Re: BUG #18887: Inner join returns non-existent data. Tom Lane 17:51
Re: BUG #18890: /src/timezone/localtime.c condition always false Tom Lane 18:02
Re: BUG #18891: /src/include/lib/simplehash.h possible palloc0 problems Tom Lane 18:04
Re: BUG #18888: /src/interfaces/ecpg/preproc/descriptor.c possible NULL dereference Euler Taveira 18:17
Re: BUG #18889: /src/backend/utils/adt/network.c condition is always false Tom Lane 18:19

April 11, 2025

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

April 12, 2025

Thread Author Time
Re: BUG #18831: Particular queries using gin-indexes are not interruptible, resulting is resource usage concerns. Vinod Sridharan 02:17
BUG #18892: When the view already exists, CREATE OR REPLACE VIEW does not check whether the table exists. PG Bug reporting form 02:34
Re: BUG #18831: Particular queries using gin-indexes are not interruptible, resulting is resource usage concerns. Tom Lane 03:00
Re: BUG #18831: Particular queries using gin-indexes are not interruptible, resulting is resource usage concerns. Vinod Sridharan 03:30
BUG #18893: Segfault during analyze pg_database PG Bug reporting form 03:34
Re: BUG #18831: Particular queries using gin-indexes are not interruptible, resulting is resource usage concerns. Tom Lane 05:33
Re: BUG #18831: Particular queries using gin-indexes are not interruptible, resulting is resource usage concerns. 📎 Vinod Sridharan 05:58
Re: BUG #18831: Particular queries using gin-indexes are not interruptible, resulting is resource usage concerns. Tom Lane 16:40
Re: BUG #18892: When the view already exists, CREATE OR REPLACE VIEW does not check whether the table exists. Kirill Reshke 19:19
Re: BUG #18892: When the view already exists, CREATE OR REPLACE VIEW does not check whether the table exists. David G. Johnston 19:32

April 13, 2025

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

April 14, 2025

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

April 15, 2025

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

April 16, 2025

Thread Author Time
Re: PostgreSQL v15.12 fails to perform PG_UPGRADE from v13 and v9 on Windows Thomas Munro 00:34
Re: BUG #18885: ERROR: corrupt MVNDistinct entry - 2 David Rowley 04:11
Re: BUG #18885: ERROR: corrupt MVNDistinct entry - 2 Andrei Lepikhov 06:57
BUG #18895: Installation failure on Fedora 42 due to missing repos PG Bug reporting form 08:59
Re: BUG #18885: ERROR: corrupt MVNDistinct entry - 2 📎 Andrei Lepikhov 10:00
Re: BUG #18895: Installation failure on Fedora 42 due to missing repos Laurenz Albe 12:20
Re: BUG #18895: Installation failure on Fedora 42 due to missing repos Devrim Gündüz 12:41
Re: BUG #18895: Installation failure on Fedora 42 due to missing repos Devrim Gündüz 13:26
Re: 回复: BUG #18892: When the view already exists, CREATE OR REPLACE VIEW does not check whether the table exists. Bruce Momjian 16:43
BUG #18896: A potential problem in heap_page_items (pageinspect, PG-17) PG Bug reporting form 20:21
BUG #18897: Logical replication conflict after using pg_createsubscriber under heavy load PG Bug reporting form 23:14
Re: BUG #18897: Logical replication conflict after using pg_createsubscriber under heavy load 📎 Zane Duffield 23:54

April 17, 2025

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

April 18, 2025

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

April 19, 2025

Thread Author Time
Re: BUG #18896: A potential problem in heap_page_items (pageinspect, PG-17) Tom Lane 19:33

April 20, 2025

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

April 21, 2025

Thread Author Time
Re: ERROR: tuple to be updated was already modified by an operation triggered by the current command Noah Misch 04:06
Re: Disabled logical replication origin session causes primary key errors Amit Kapila 05:17
Re: BUG #18897: Logical replication conflict after using pg_createsubscriber under heavy load Amit Kapila 06:09
Re: BUG #18897: Logical replication conflict after using pg_createsubscriber under heavy load Shlok Kyal 06:40
Re: BUG #18885: ERROR: corrupt MVNDistinct entry - 2 Tomas Vondra 09:41
RE: Disabled logical replication origin session causes primary key errors 📎 Hayato Kuroda (Fujitsu) 10:08
Command order bug in pg_dump Kirill Reshke 10:56
Re: BUG #18885: ERROR: corrupt MVNDistinct entry - 2 David Rowley 12:11
[No subject] Александр Иванов 14:23
Re: Command order bug in pg_dump Tom Lane 14:56
Re: Disabled logical replication origin session causes primary key errors vignesh C 16:17
Re: Disabled logical replication origin session causes primary key errors Masahiko Sawada 17:00
Re: Command order bug in pg_dump Tom Lane 17:08
Re: Command order bug in pg_dump Kirill Reshke 17:30
Re: Command order bug in pg_dump Kirill Reshke 17:33
Re: Command order bug in pg_dump Alvaro Herrera 17:44
Re: Command order bug in pg_dump 📎 Tom Lane 19:41
Re: BUG #18885: ERROR: corrupt MVNDistinct entry - 2 📎 Alexander Korotkov 20:23

April 22, 2025

Thread Author Time
Re: Disabled logical replication origin session causes primary key errors Amit Kapila 02:35
RE: Disabled logical replication origin session causes primary key errors 📎 Hayato Kuroda (Fujitsu) 09:06
Re: Disabled logical replication origin session causes primary key errors vignesh C 09:36
BUG #18900: Missing RPM python3-kazoo for RHEL9 - patroni RPM cannot be installed PG Bug reporting form 09:38
Re: PostgreSQL v15.12 fails to perform PG_UPGRADE from v13 and v9 on Windows Avi Uziel 10:58
RE: Disabled logical replication origin session causes primary key errors 📎 Hayato Kuroda (Fujitsu) 11:00
Re: PostgreSQL v15.12 fails to perform PG_UPGRADE from v13 and v9 on Windows Manika Singhal 11:30
Re: PostgreSQL v15.12 fails to perform PG_UPGRADE from v13 and v9 on Windows Avi Uziel 11:39
Re: BUG #18900: Missing RPM python3-kazoo for RHEL9 - patroni RPM cannot be installed Robert Treat 12:27
Re: Disabled logical replication origin session causes primary key errors vignesh C 13:37
Re: BUG #18872: The current OS X version is not supported Dave Cramer 13:40
BUG #18901: Bug in Perl-Script "src/backend/nodes/gen_node_support.pl" PG Bug reporting form 16:39
Re: BUG #18901: Bug in Perl-Script "src/backend/nodes/gen_node_support.pl" Tom Lane 17:25
Re: Disabled logical replication origin session causes primary key errors Masahiko Sawada 18:10
Re: Command order bug in pg_dump Alvaro Herrera 19:08
Re: Command order bug in pg_dump Tom Lane 19:14
Re: Disabled logical replication origin session causes primary key errors Shawn McCoy 20:10
Re: Command order bug in pg_dump 📎 Tom Lane 20:53

April 23, 2025

Thread Author Time
RE: Disabled logical replication origin session causes primary key errors 📎 Hayato Kuroda (Fujitsu) 01:41
Re: BUG #18897: Logical replication conflict after using pg_createsubscriber under heavy load Euler Taveira 01:57
Re: Command order bug in pg_dump Kirill Reshke 02:59
Re: BUG #18897: Logical replication conflict after using pg_createsubscriber under heavy load Zane Duffield 03:13
Re: BUG #18897: Logical replication conflict after using pg_createsubscriber under heavy load Zane Duffield 03:30
BUG #18902: TRAP:: failed Assert("!is_sorted") in File: "createplan.c" PG Bug reporting form 04:48
Re: PostgreSQL v15.12 fails to perform PG_UPGRADE from v13 and v9 on Windows Manika Singhal 05:40
Re: BUG #18885: ERROR: corrupt MVNDistinct entry - 2 Andrei Lepikhov 06:52
Re: Disabled logical replication origin session causes primary key errors Amit Kapila 09:01
Re: BUG #18902: TRAP:: failed Assert("!is_sorted") in File: "createplan.c" Tender Wang 11:03
Re: BUG #18902: TRAP:: failed Assert("!is_sorted") in File: "createplan.c" Tender Wang 11:47
Re: Command order bug in pg_dump Alvaro Herrera 13:01
Re: Command order bug in pg_dump Tom Lane 14:41
Re: Disabled logical replication origin session causes primary key errors Masahiko Sawada 15:58

April 24, 2025

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

Browse Archives

Prev | Next