pgsql-bugs - December 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)
Advanced Search

Browse Archives

Prev | Next
Jump to day: 1 2 3 4 5 6 8 9 10 11 12 13 14 15 16 17 18 19 22 23 24 25 26 27 28 29 30 31

Dec. 1, 2025

Thread Author Time
Re: BUG #19095: Test if function exit() is used fail when linked static VASUKI M 04:57
Re: BUG #19335: the function encrypt does not work correct - ERROR: encrypt error: Key was too big Daniel Gustafsson 09:03
BUG #19338: [PG15] Unstable SQL result in test regress/tablespace PG Bug reporting form 11:31
Re: BUG #19338: [PG15] Unstable SQL result in test regress/tablespace Tom Lane 15:54
Re: BUG #19338: [PG15] Unstable SQL result in test regress/tablespace Dmitry Kovalenko 16:52
BUG #19339: odbc_fdw extension, Not able to read data from foreign tables PG Bug reporting form 20:11

Dec. 2, 2025

Thread Author Time
BUG #19340: Wrong result from CORR() function PG Bug reporting form 07:57
BUG #19341: REPLACE() fails to match final character when using nondeterministic ICU collation PG Bug reporting form 10:03
Re: BUG #19340: Wrong result from CORR() function Laurenz Albe 11:30
BUG #19342: ERROR: function gcd(smallint, smallint) is not unique PG Bug reporting form 13:02
Re: BUG #19342: ERROR: function gcd(smallint, smallint) is not unique Daniel Gustafsson 13:36
Re: BUG #19340: Wrong result from CORR() function Oleg Ivanov 14:05
Re: BUG #19341: REPLACE() fails to match final character when using nondeterministic ICU collation Laurenz Albe 16:24
Re: BUG #19341: REPLACE() fails to match final character when using nondeterministic ICU collation 📎 Laurenz Albe 16:31
Re: BUG #19341: REPLACE() fails to match final character when using nondeterministic ICU collation Heikki Linnakangas 16:36
Re: BUG #19341: REPLACE() fails to match final character when using nondeterministic ICU collation 📎 Laurenz Albe 17:18
Re: BUG #19340: Wrong result from CORR() function Tom Lane 17:22
Re: BUG #19340: Wrong result from CORR() function Laurenz Albe 17:22
Re: BUG #19341: REPLACE() fails to match final character when using nondeterministic ICU collation Tom Lane 17:25
Re: BUG #19341: REPLACE() fails to match final character when using nondeterministic ICU collation Heikki Linnakangas 17:29
Re: BUG #19341: REPLACE() fails to match final character when using nondeterministic ICU collation Laurenz Albe 17:45
Re: BUG #19341: REPLACE() fails to match final character when using nondeterministic ICU collation 📎 Laurenz Albe 17:51
Re: BUG #19340: Wrong result from CORR() function Dean Rasheed 18:54
BUG #19343: toast_internals.c:139:2: warning: missing braces around initializer [-Wmissing-braces] PG Bug reporting form 19:41
Re: BUG #19340: Wrong result from CORR() function 📎 Tom Lane 20:26
Re: BUG #19341: REPLACE() fails to match final character when using nondeterministic ICU collation Tom Lane 20:53
Re: BUG #19341: REPLACE() fails to match final character when using nondeterministic ICU collation Laurenz Albe 21:44
Re: BUG #19340: Wrong result from CORR() function Dean Rasheed 23:03
Re: BUG #19340: Wrong result from CORR() function Tom Lane 23:24
Re: BUG #19340: Wrong result from CORR() function Dean Rasheed 23:48

Dec. 3, 2025

Thread Author Time
Re: BUG #19340: Wrong result from CORR() function 📎 Tom Lane 00:17
Re: BUG #19340: Wrong result from CORR() function Tom Lane 01:27
Re: BUG #19341: REPLACE() fails to match final character when using nondeterministic ICU collation 📎 Laurenz Albe 07:51
Re: BUG #19343: toast_internals.c:139:2: warning: missing braces around initializer [-Wmissing-braces] Heikki Linnakangas 09:13
Re: BUG #19340: Wrong result from CORR() function Dean Rasheed 11:38
Re: BUG #19095: Test if function exit() is used fail when linked static 📎 VASUKI M 11:59
Re: BUG #19341: REPLACE() fails to match final character when using nondeterministic ICU collation Tom Lane 15:12
Re: BUG #19340: Wrong result from CORR() function Tom Lane 16:33
Re: BUG #19340: Wrong result from CORR() function 📎 Tom Lane 22:52
Re: BUG #19095: Test if function exit() is used fail when linked static Daniel Gustafsson 23:33

Dec. 4, 2025

Thread Author Time
Re: BUG #19340: Wrong result from CORR() function Tom Lane 00:11
Re: BUG #19095: Test if function exit() is used fail when linked static 📎 Michael Paquier 00:32
Re: BUG #19332: Sudden 330x performance degradation of SELECT amid INSERTs 📎 Sergey Naumov 10:19
Re: BUG #19095: Test if function exit() is used fail when linked static 📎 VASUKI M 11:08
Segfault due to NULL ParamExecData value Anthonin Bonnefoy 14:25
Re: Segfault due to NULL ParamExecData value Tom Lane 15:35
Re: BUG #19341: REPLACE() fails to match final character when using nondeterministic ICU collation 📎 Laurenz Albe 17:14

Dec. 5, 2025

Thread Author Time
Re: BUG #19095: Test if function exit() is used fail when linked static Michael Paquier 00:41
Re：GROUP BY ROLLUP queries on views trigger full table scans (index usage not optimized) Haowu Ge 02:17
BUG #19345: MemoryContextSizeFailure after upgrade 14.11 to 17.7 in stored procedure PG Bug reporting form 02:41
Re: BUG #19340: Wrong result from CORR() function Dean Rasheed 09:23
Re: BUG #19340: Wrong result from CORR() function Dean Rasheed 10:17
Re: Segfault due to NULL ParamExecData value Anthonin Bonnefoy 13:33
Re: BUG #19345: MemoryContextSizeFailure after upgrade 14.11 to 17.7 in stored procedure Kirill Reshke 13:36
Re: BUG #19340: Wrong result from CORR() function 📎 Tom Lane 22:17

Dec. 6, 2025

Thread Author Time
Re: BUG #19341: REPLACE() fails to match final character when using nondeterministic ICU collation Tom Lane 01:12
Re: BUG #19340: Wrong result from CORR() function Tom Lane 06:09
Re: BUG #19340: Wrong result from CORR() function Dean Rasheed 11:51
Re: BUG #19340: Wrong result from CORR() function 📎 Tom Lane 18:18
Re: BUG #19345: MemoryContextSizeFailure after upgrade 14.11 to 17.7 in stored procedure Tom Lane 21:04
Re: BUG #19340: Wrong result from CORR() function Dean Rasheed 22:53
Re: BUG #19340: Wrong result from CORR() function Tom Lane 23:32

Dec. 8, 2025

Thread Author Time
Re: BUG #19095: Test if function exit() is used fail when linked static VASUKI M 04:41
Re: GROUP BY ROLLUP queries on views trigger full table scans (index usage not optimized) Richard Guo 06:10

Dec. 9, 2025

Thread Author Time
Re: BUG #19095: Test if function exit() is used fail when linked static Michael Paquier 04:16
Re: BUG #19095: Test if function exit() is used fail when linked static Peter Eisentraut 06:10
Re: BUG #19095: Test if function exit() is used fail when linked static 📎 Michael Paquier 06:26
Re: GROUP BY ROLLUP queries on views trigger full table scans (index usage not optimized) 📎 Richard Guo 06:38
Re: GROUP BY ROLLUP queries on views trigger full table scans (index usage not optimized) Haowu Ge 08:54
Re: BUG #19095: Test if function exit() is used fail when linked static VASUKI M 10:23
BUG #19348: Disk space error when running COPY after upgrading to PostgreSQL 17.7 PG Bug reporting form 11:04
Re: BUG #19345: MemoryContextSizeFailure after upgrade 14.11 to 17.7 in stored procedure weijie JL 11:30
Re: BUG #19095: Test if function exit() is used fail when linked static Bilal Yavuz 12:47
Re: BUG #19348: Disk space error when running COPY after upgrading to PostgreSQL 17.7 Greg Sabino Mullane 14:28
Re: BUG #19348: Disk space error when running COPY after upgrading to PostgreSQL 17.7 Thomas Munro 21:19
Re: BUG #19095: Test if function exit() is used fail when linked static Michael Paquier 23:11

Dec. 10, 2025

Thread Author Time
Re: BUG #19348: Disk space error when running COPY after upgrading to PostgreSQL 17.7 weijie JL 01:07
Re: GROUP BY ROLLUP queries on views trigger full table scans (index usage not optimized) Richard Guo 02:01
Re: BUG #19007: Planner fails to choose partial index with spurious 'not null' Richard Guo 02:11
Re: BUG #19332: Sudden 330x performance degradation of SELECT amid INSERTs David Rowley 03:46
Re: BUG #19095: Test if function exit() is used fail when linked static Michael Paquier 05:14
Re: BUG #19341: REPLACE() fails to match final character when using nondeterministic ICU collation Laurenz Albe 10:03
BUG #19350: Short circuit optimization missed when running sql scriptes in JDBC PG Bug reporting form 10:31
Re: BUG #19332: Sudden 330x performance degradation of SELECT amid INSERTs Sergey Naumov 10:33
Re: BUG #19339: odbc_fdw extension, Not able to read data from foreign tables Etsuro Fujita 11:41
Re: BUG #19350: Short circuit optimization missed when running sql scriptes in JDBC David G. Johnston 13:33
Re: BUG #19350: Short circuit optimization missed when running sqlscriptes in JDBC ZhangChi 13:41
Re: BUG #19350: Short circuit optimization missed when running sql scriptes in JDBC David G. Johnston 13:46
Re: BUG #19350: Short circuit optimization missed when running sqlscriptes in JDBC ZhangChi 14:01
BUG #19351: in pg18.1,when not null exists in the table , and add constraint problem. PG Bug reporting form 14:51
Re: BUG #19339: odbc_fdw extension, Not able to read data from foreign tables Vijay Reddy 15:50
Re: BUG #19351: in pg18.1,when not null exists in the table , and add constraint problem. Srinath Reddy Sadipiralla 16:02
Re: BUG #19350: Short circuit optimization missed when running sqlscriptes in JDBC Tom Lane 16:07
Re: BUG #19351: in pg18.1,when not null exists in the table , and add constraint problem. Srinath Reddy Sadipiralla 16:40

Dec. 11, 2025

Thread Author Time
Re: GROUP BY ROLLUP queries on views trigger full table scans (index usage not optimized) 📎 Haowu Ge 02:32
Re: BUG #19006: Assert(BufferIsPinned) in BufferGetBlockNumber() is triggered for forwarded buffer Xuneng Zhou 04:16
Re: BUG #19351: in pg18.1,when not null exists in the table , and add constraint problem. Álvaro Herrera 07:27
Re: BUG #19351: in pg18.1,when not null exists in the table , and add constraint problem. Álvaro Herrera 07:29
Re: BUG #19339: odbc_fdw extension, Not able to read data from foreign tables Etsuro Fujita 11:01

Dec. 12, 2025

Thread Author Time
BUG #19352: SQL Error messages do not include schema name along with table or data object name. PG Bug reporting form 02:14
Re: BUG #19352: SQL Error messages do not include schema name along with table or data object name. Kirill Reshke 09:00
Re: GROUP BY ROLLUP queries on views trigger full table scans (index usage not optimized) 📎 Richard Guo 09:28
BUG #19353: Error XX000 if referencing expanded array in grouping set: variable not found in subplan target list PG Bug reporting form 10:11
Re:Re: BUG #19351: in pg18.1,when not null exists in the table , and add constraint problem. yanliang lei 10:23
Bug in sub-query Veeranjaneya Vara Prasad Peddireddy 10:59
Re: Re: BUG #19351: in pg18.1,when not null exists in the table , and add constraint problem. Álvaro Herrera 15:01
Re: BUG #19352: SQL Error messages do not include schema name along with table or data object name. Álvaro Herrera 15:10
Re: Bug in sub-query Tom Lane 15:26
Re: BUG #19352: SQL Error messages do not include schema name along with table or data object name. Tom Lane 15:39
Re: BUG #19353: Error XX000 if referencing expanded array in grouping set: variable not found in subplan target list Tom Lane 16:54

Dec. 13, 2025

Thread Author Time
Re:Re: Re: BUG #19351: in pg18.1,when not null exists in the table , and add constraint problem. yanliang lei 04:15
Re: BUG #19353: Error XX000 if referencing expanded array in grouping set: variable not found in subplan target list Tender Wang 10:01
recovery_target discrepancy? Thomas Rosenstein 12:18
Re: Re: Re: BUG #19351: in pg18.1,when not null exists in the table , and add constraint problem. 📎 Álvaro Herrera 12:44
BUG #19354: JOHAB rejects valid byte sequences PG Bug reporting form 18:52
Cluster is not being created T iv 19:34

Dec. 14, 2025

Thread Author Time
Re: Re: Re: BUG #19351: in pg18.1,when not null exists in the table , and add constraint problem. Srinath Reddy Sadipiralla 17:00

Dec. 15, 2025

Thread Author Time
Re: GROUP BY ROLLUP queries on views trigger full table scans (index usage not optimized) 📎 Haowu Ge 01:23
BUG #19355: Attempt to insert data unexpectedly during concurrent update PG Bug reporting form 01:40
Re: BUG #19355: Attempt to insert data unexpectedly during concurrent update Laurenz Albe 06:25
Re: BUG #19353: Error XX000 if referencing expanded array in grouping set: variable not found in subplan target list 📎 Richard Guo 14:28
Re: Cluster is not being created Robert Haas 16:50
Re: BUG #19354: JOHAB rejects valid byte sequences Robert Haas 17:46
Re: BUG #19332: Sudden 330x performance degradation of SELECT amid INSERTs 📎 David Rowley 19:35

Dec. 16, 2025

Thread Author Time
Re: BUG #19354: JOHAB rejects valid byte sequences Jeroen Vermeulen 00:07
Re: BUG #19354: JOHAB rejects valid byte sequences Tom Lane 00:56
BUG #19356: Unexpected result of prepared UPDATE with force_generic_plan PG Bug reporting form 03:06
Re: BUG #19354: JOHAB rejects valid byte sequences VASUKI M 06:23
Re: BUG #19354: JOHAB rejects valid byte sequences Jeroen Vermeulen 07:42
Re: BUG #19353: Error XX000 if referencing expanded array in grouping set: variable not found in subplan target list Tender Wang 11:30
Re: BUG #19354: JOHAB rejects valid byte sequences Robert Haas 14:26
Re: BUG #19350: Short circuit optimization missed when running sqlscriptes in JDBC Greg Sabino Mullane 15:17
Re: BUG #19354: JOHAB rejects valid byte sequences Tom Lane 15:41
Re: BUG #19354: JOHAB rejects valid byte sequences Robert Haas 18:42

Dec. 17, 2025

Thread Author Time
Possible performance issues: DISTINCT ON + ORDER BY and JIT with aggregation Jhonathan Cruz 00:25
Re: BUG #19350: Short circuit optimization missed when runningsqlscriptes in JDBC ZhangChi 01:40
Re: BUG #19354: JOHAB rejects valid byte sequences Michael Paquier 02:59
Re: Cluster is not being created VASUKI M 05:32
BUG #19357: PostgreSQL generates a custom plan that performs worse than the generic plan for a certain query. PG Bug reporting form 06:57
BUG #19358: Short circuit optimization exists in generic plan but missed in custom plan PG Bug reporting form 12:03
Re: BUG #19350: Short circuit optimization missed when runningsqlscriptes in JDBC Dave Cramer 12:55
Re: BUG #19350: Short circuit optimization missed when runningsqlscriptes in JDBC Greg Sabino Mullane 14:51
Re: BUG #19357: PostgreSQL generates a custom plan that performs worse than the generic plan for a certain query. Greg Sabino Mullane 14:54
Re: Possible performance issues: DISTINCT ON + ORDER BY and JIT with aggregation Laurenz Albe 15:14
Re: BUG #19357: PostgreSQL generates a custom plan that performsworse than the generic plan for a certain query. ZhangChi 15:17
Re: BUG #19350: Short circuit optimization missed when runningsqlscriptes in JDBC Dave Cramer 15:33
Re: BUG #19357: PostgreSQL generates a custom plan that performs worse than the generic plan for a certain query. Tom Lane 15:39
Re: BUG #19350: Short circuit optimization missed when runningsqlscriptes in JDBC Dave Cramer 15:39
Re: BUG #19350: Short circuit optimization missed when runningsqlscriptes in JDBC Tom Lane 15:44
Re: BUG #19357: PostgreSQL generates a custom plan that performs worse than the generic plan for a certain query. ZhangChi 15:52
Re: BUG #19357: PostgreSQL generates a custom plan that performsworse than the generic plan for a certain query. Pavel Stehule 15:53
Re: BUG #19357: PostgreSQL generates a custom plan that performsworsethan the generic plan for a certain query. ZhangChi 16:08
Re: BUG #19357: PostgreSQL generates a custom plan that performsworsethan the generic plan for a certain query. Pavel Stehule 16:15
Re: BUG #19357: PostgreSQL generates a custom plan thatperformsworsethan the generic plan for a certain query. ZhangChi 16:20
Re: BUG #19357: PostgreSQL generates a custom plan thatperformsworsethan the generic plan for a certain query. Pavel Stehule 16:33
Re: BUG #19357: PostgreSQL generates a custom plan that performsworsethan the generic plan for a certain query. Greg Sabino Mullane 17:11
Re: BUG #19358: Short circuit optimization exists in generic plan but missed in custom plan Tom Lane 21:37

Dec. 18, 2025

Thread Author Time
[BUG] PostgreSQL 14.5: Data corruption in table tb_workstation_message (possible fstrim-related on eMMC) 第108次明天 06:42
Re: [BUG] PostgreSQL 14.5: Data corruption in table tb_workstation_message (possible fstrim-related on eMMC) Laurenz Albe 08:40
Re: GROUP BY ROLLUP queries on views trigger full table scans (index usage not optimized) Richard Guo 08:56
Re: [BUG] PostgreSQL 14.5: Data corruption in table tb_workstation_message (possible fstrim-related on eMMC) Greg Sabino Mullane 13:30
BUG #19359: Row level security: Upserts require insert policies in the update path PG Bug reporting form 15:03

Dec. 19, 2025

Thread Author Time
Re: BUG #19359: Row level security: Upserts require insert policies in the update path Srinath Reddy Sadipiralla 17:40
Re: BUG #19359: Row level security: Upserts require insert policies in the update path Dean Rasheed 23:12

Dec. 22, 2025

Thread Author Time
BUG #19360: Bug Report: Logical Replication initial sync fails with "conflict=update_origin_differs" PG12 toPG18 PG Bug reporting form 08:55
Re: BUG #19355: Attempt to insert data unexpectedly during concurrent update Bh W 14:51
Re: BUG #19355: Attempt to insert data unexpectedly during concurrent update Dean Rasheed 22:37

Dec. 23, 2025

Thread Author Time
Re: BUG #19360: Bug Report: Logical Replication initial sync fails with "conflict=update_origin_differs" PG12 toPG18 Rahila Syed 07:49
BUG #19362: Extremely log processing of jsonb_path_exists_opr PG Bug reporting form 18:21
Re: BUG #19362: Extremely log processing of jsonb_path_exists_opr Andrey Rachitskiy 19:02

Dec. 24, 2025

Thread Author Time
Re: BUG #19353: Error XX000 if referencing expanded array in grouping set: variable not found in subplan target list Richard Guo 02:15
Re: BUG #19353: Error XX000 if referencing expanded array in grouping set: variable not found in subplan target list Tender Wang 02:40
Re: GROUP BY ROLLUP queries on views trigger full table scans (index usage not optimized) 📎 Richard Guo 07:50
Re: BUG #19355: Attempt to insert data unexpectedly during concurrent update Amit Langote 08:08
Re: GROUP BY ROLLUP queries on views trigger full table scans (index usage not optimized) Haowu Ge 10:05
Re: BUG #19355: Attempt to insert data unexpectedly during concurrent update 📎 Tender Wang 12:07
Regression: partial index with IS NOT NULL predicate not used for min/max optimization on NOT NULL columns 📎 Dmytro Astapov 16:46
Re: Regression: partial index with IS NOT NULL predicate not used for min/max optimization on NOT NULL columns Tom Lane 17:13
Re: Regression: partial index with IS NOT NULL predicate not used for min/max optimization on NOT NULL columns Dmytro Astapov 18:43
Re: BUG #19355: Attempt to insert data unexpectedly during concurrent update 📎 Dean Rasheed 23:11

Dec. 25, 2025

Thread Author Time
Re: BUG #19353: Error XX000 if referencing expanded array in grouping set: variable not found in subplan target list Richard Guo 03:58
Re: BUG #19355: Attempt to insert data unexpectedly during concurrent update Tender Wang 04:48

Dec. 26, 2025

Thread Author Time
Re: BUG #19356: Unexpected result of prepared UPDATE with force_generic_plan ZhangChi 06:59
Re: BUG #19356: Unexpected result of prepared UPDATE with force_generic_plan Tender Wang 07:20
Re: BUG #19356: Unexpected result of prepared UPDATE with force_generic_plan ZhangChi 07:59
Re: Standby server with cascade logical replication could not be properly stopped under load G. Sl 11:14
BUG #19363: PostgreSQL shared memory exhaustion during query execution involving views and parallel workers PG Bug reporting form 15:07
BUG #19364: Repository not updating PG Bug reporting form 21:10

Dec. 27, 2025

Thread Author Time
Re: BUG #19363: PostgreSQL shared memory exhaustion during query execution involving views and parallel workers Richard Guo 05:12
Re: BUG #19363: PostgreSQL shared memory exhaustion during query execution involving views and parallel workers Tom Lane 17:02
Re: BUG #19363: PostgreSQL shared memory exhaustion during query execution involving views and parallel workers Tom Lane 21:33
BUG #19365: postgres 18 pg_dump fails whan drop sequence concurrently PG Bug reporting form 23:57

Dec. 28, 2025

Thread Author Time
Re: GROUP BY ROLLUP queries on views trigger full table scans (index usage not optimized) Richard Guo 04:20
Re: BUG #19360: Bug Report: Logical Replication initial sync fails with "conflict=update_origin_differs" PG12 toPG18 Amit Kapila 06:48
Re: GROUP BY ROLLUP queries on views trigger full table scans (index usage not optimized) Tom Lane 16:51
Lost update in an ordered batch, but only with index scan Bernice Southey 23:07

Dec. 29, 2025

Thread Author Time
Re: Standby server with cascade logical replication could not be properly stopped under load Michael Paquier 00:09
Re: Standby server with cascade logical replication could not be properly stopped under load G. Sl 05:22
BUG #19366: heap-use-after-free in pgaio_io_reclaim() detected with RELCACHE_FORCE_RELEASE PG Bug reporting form 06:00
Re: Lost update in an ordered batch, but only with index scan Richard Guo 08:12

Browse Archives

Prev | Next
Jump to day: 1 2 3 4 5 6 8 9 10 11 12 13 14 15 16 17 18 19 22 23 24 25 26 27 28 29 30 31