pg.ddx.io pgsql-bugs@postgresql.org mailing list archive
help / color / mirror / Atom feedBUG #19415: Spelling error about 'vacuume' in zh_CN.po
2026-02-25 06:22 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #19415: Spelling error about 'vacuume' in zh_CN.po
2026-02-25 16:05 UTC Bruce Momjian <bruce@momjian.us>
[2+ messages in thread]
[PATCH 1/2] Test specinsert cleanup in ReorderBufferProcessTXN error path
2026-02-25 09:47 UTC Vishal Prasanna <vishal.g@zohocorp.com>
` [PATCH 1/2] Test specinsert cleanup in ReorderBufferProcessTXN error path
2026-02-25 15:09 UTC Vishal Prasanna <vishal.g@zohocorp.com>
[2+ messages in thread]
BugReport: PostgreSQL 17.8. Processing UTF8 encoded strings
2026-02-25 06:50 UTC Vladimir Valikaev <vladimir@4vrs.com>
` Re: BugReport: PostgreSQL 17.8. Processing UTF8 encoded strings
2026-02-25 13:59 UTC David G. Johnston <david.g.johnston@gmail.com>
[2+ messages in thread]
BUG #18985: fast shutdown does not close connections from qlik data gateway data movement aka. replicate
2025-07-15 10:23 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18985: fast shutdown does not close connections from qlik data gateway data movement aka. replicate
2025-07-15 14:35 UTC David G. Johnston <david.g.johnston@gmail.com>
` Re: BUG #18985: fast shutdown does not close connections from qlik data gateway data movement aka. replicate
2025-07-15 14:57 UTC Erik Dobák <erik.dobak@gmail.com>
` Re: BUG #18985: fast shutdown does not close connections from qlik data gateway data movement aka. replicate
2025-07-15 14:59 UTC Erik Dobák <erik.dobak@gmail.com>
` Re: BUG #18985: fast shutdown does not close connections from qlik data gateway data movement aka. replicate
2025-07-15 16:08 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #18985: fast shutdown does not close connections from qlik data gateway data movement aka. replicate
2025-07-15 16:22 UTC Erik Dobák <erik.dobak@gmail.com>
` Re: BUG #18985: fast shutdown does not close connections from qlik data gateway data movement aka. replicate
2025-07-15 16:27 UTC David G. Johnston <david.g.johnston@gmail.com>
` Re: BUG #18985: fast shutdown does not close connections from qlik data gateway data movement aka. replicate
2025-07-15 18:00 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #18985: fast shutdown does not close connections from qlik data gateway data movement aka. replicate
2025-07-15 18:27 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #18985: fast shutdown does not close connections from qlik data gateway data movement aka. replicate
2025-07-15 18:28 UTC David G. Johnston <david.g.johnston@gmail.com>
` Re: BUG #18985: fast shutdown does not close connections from qlik data gateway data movement aka. replicate
2025-07-15 18:32 UTC Erik Dobák <erik.dobak@gmail.com>
` Re: BUG #18985: fast shutdown does not close connections from qlik data gateway data movement aka. replicate
2025-07-15 18:38 UTC Erik Dobák <erik.dobak@gmail.com>
` Re: BUG #18985: fast shutdown does not close connections from qlik data gateway data movement aka. replicate
2026-02-25 09:08 UTC Anthonin Bonnefoy <anthonin.bonnefoy@datadoghq.com>
[13+ messages in thread]
BUG #19414: Wrong rows returned by index scan on HASH-partitioned table with PRIMARY KEY (PostgreSQL 16.9)
2026-02-19 12:24 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #19414: Wrong rows returned by index scan on HASH-partitioned table with PRIMARY KEY (PostgreSQL 16.9)
2026-02-23 19:04 UTC Rafia Sabih <rafia.pghackers@gmail.com>
` Re: BUG #19414: Wrong rows returned by index scan on HASH-partitioned table with PRIMARY KEY (PostgreSQL 16.9)
2026-02-23 20:23 UTC Álvaro Herrera <alvherre@kurilemu.de>
` Re: BUG #19414: Wrong rows returned by index scan on HASH-partitioned table with PRIMARY KEY (PostgreSQL 16.9)
2026-02-24 09:26 UTC José Antonio Morcillo Valenciano <jose.morcillo.valenciano@gmail.com>
` Re: BUG #19414: Wrong rows returned by index scan on HASH-partitioned table with PRIMARY KEY (PostgreSQL 16.9)
2026-02-24 12:18 UTC Álvaro Herrera <alvherre@kurilemu.de>
[5+ messages in thread]
BUG #19393: pg_upgrade fails with duplicate key violation when CHECK constraint named *_not_null exists
2026-02-04 17:33 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #19393: pg_upgrade fails with duplicate key violation when CHECK constraint named *_not_null exists
2026-02-05 14:58 UTC Laurenz Albe <laurenz.albe@cybertec.at>
` Re: BUG #19393: pg_upgrade fails with duplicate key violation when CHECK constraint named *_not_null exists
2026-02-05 16:52 UTC Laurenz Albe <laurenz.albe@cybertec.at>
` Re: BUG #19393: pg_upgrade fails with duplicate key violation when CHECK constraint named *_not_null exists
2026-02-06 07:23 UTC Dilip Kumar <dilipbalaut@gmail.com>
` Re: BUG #19393: pg_upgrade fails with duplicate key violation when CHECK constraint named *_not_null exists
2026-02-06 09:10 UTC Laurenz Albe <laurenz.albe@cybertec.at>
` Re: BUG #19393: pg_upgrade fails with duplicate key violation when CHECK constraint named *_not_null exists
2026-02-06 10:46 UTC Dilip Kumar <dilipbalaut@gmail.com>
` Re: BUG #19393: pg_upgrade fails with duplicate key violation when CHECK constraint named *_not_null exists
2026-02-09 06:24 UTC Hüseyin Demir <huseyin.d3r@gmail.com>
` Re: BUG #19393: pg_upgrade fails with duplicate key violation when CHECK constraint named *_not_null exists
2026-02-09 11:01 UTC Laurenz Albe <laurenz.albe@cybertec.at>
` Re: BUG #19393: pg_upgrade fails with duplicate key violation when CHECK constraint named *_not_null exists
2026-02-09 17:16 UTC Hüseyin Demir <huseyin.d3r@gmail.com>
` Re: BUG #19393: pg_upgrade fails with duplicate key violation when CHECK constraint named *_not_null exists
2026-02-10 00:37 UTC Michael Paquier <michael@paquier.xyz>
` Re: BUG #19393: pg_upgrade fails with duplicate key violation when CHECK constraint named *_not_null exists
2026-02-20 06:52 UTC Hüseyin Demir <huseyin.d3r@gmail.com>
` Re: BUG #19393: pg_upgrade fails with duplicate key violation when CHECK constraint named *_not_null exists
2026-02-21 11:56 UTC Álvaro Herrera <alvherre@kurilemu.de>
` Re: BUG #19393: pg_upgrade fails with duplicate key violation when CHECK constraint named *_not_null exists
2026-02-21 13:45 UTC Álvaro Herrera <alvherre@kurilemu.de>
` Re: BUG #19393: pg_upgrade fails with duplicate key violation when CHECK constraint named *_not_null exists
2026-02-21 15:13 UTC Laurenz Albe <laurenz.albe@cybertec.at>
` Re: BUG #19393: pg_upgrade fails with duplicate key violation when CHECK constraint named *_not_null exists
2026-02-22 03:40 UTC Michael Paquier <michael@paquier.xyz>
` Re: BUG #19393: pg_upgrade fails with duplicate key violation when CHECK constraint named *_not_null exists
2026-02-23 16:47 UTC Álvaro Herrera <alvherre@kurilemu.de>
` Re: BUG #19393: pg_upgrade fails with duplicate key violation when CHECK constraint named *_not_null exists
2026-02-23 23:20 UTC Michael Paquier <michael@paquier.xyz>
[17+ messages in thread]
BUG: SUBSTRING on TOASTed text returns "invalid byte sequence for encoding UTF8: 0xc3"
2026-02-20 23:58 UTC ludovitkramar <ludovitkramar@proton.me>
` Re: BUG: SUBSTRING on TOASTed text returns "invalid byte sequence for encoding UTF8: 0xc3"
2026-02-21 15:05 UTC David G. Johnston <david.g.johnston@gmail.com>
[2+ messages in thread]
BUG #19412: Wrong query result with not null constraint
2026-02-17 11:19 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #19412: Wrong query result with not null constraint
2026-02-17 12:14 UTC Artem Fadeev <a.fadeev@postgrespro.ru>
` Re: BUG #19412: Wrong query result with not null constraint
2026-02-17 22:53 UTC David Rowley <dgrowleyml@gmail.com>
` Re: BUG #19412: Wrong query result with not null constraint
2026-02-18 01:51 UTC Richard Guo <guofenglinux@gmail.com>
` Re: BUG #19412: Wrong query result with not null constraint
2026-02-18 09:50 UTC Richard Guo <guofenglinux@gmail.com>
` Re: BUG #19412: Wrong query result with not null constraint
2026-02-18 12:03 UTC Sergey Shinderuk <s.shinderuk@postgrespro.ru>
` Re: BUG #19412: Wrong query result with not null constraint
2026-02-19 01:49 UTC Richard Guo <guofenglinux@gmail.com>
` Re: BUG #19412: Wrong query result with not null constraint
2026-02-19 02:18 UTC Richard Guo <guofenglinux@gmail.com>
` Re: BUG #19412: Wrong query result with not null constraint
2026-02-19 18:25 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #19412: Wrong query result with not null constraint
2026-02-20 09:57 UTC Richard Guo <guofenglinux@gmail.com>
` Re: BUG #19412: Wrong query result with not null constraint
2026-02-20 10:54 UTC Sergey Shinderuk <s.shinderuk@postgrespro.ru>
[11+ messages in thread]
BUG #19396: Standby and DR site replication broken with PANIC: WAL contains references to invalid pages messge
2026-02-09 07:31 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #19396: Standby and DR site replication broken with PANIC: WAL contains references to invalid pages messge
2026-02-10 00:34 UTC Michael Paquier <michael@paquier.xyz>
` Re: BUG #19396: Standby and DR site replication broken with PANIC: WAL contains references to invalid pages messge
2026-02-10 04:22 UTC Ishan joshi <ishanjoshi@live.com>
` Re: BUG #19396: Standby and DR site replication broken with PANIC: WAL contains references to invalid pages messge
2026-02-20 10:39 UTC Ishan joshi <ishanjoshi@live.com>
[4+ messages in thread]
Error "could not access status of transaction" - version 14.21
2026-02-19 14:47 UTC Aaron Caskey-Demaret <aaron.caskey-demaret@nshift.com>
` Re: Error "could not access status of transaction" - version 14.21
2026-02-19 17:34 UTC Kirill Reshke <reshkekirill@gmail.com>
[2+ messages in thread]
BUG #19409: Function jsonb_strip_nulls() changed from immutable to stable.
2026-02-13 19:51 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #19409: Function jsonb_strip_nulls() changed from immutable to stable.
2026-02-13 20:18 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #19409: Function jsonb_strip_nulls() changed from immutable to stable.
2026-02-13 21:35 UTC Florents Tselai <florents.tselai@gmail.com>
` Re: BUG #19409: Function jsonb_strip_nulls() changed from immutable to stable.
2026-02-16 16:18 UTC Andrew Dunstan <andrew@dunslane.net>
` Re: BUG #19409: Function jsonb_strip_nulls() changed from immutable to stable.
2026-02-16 16:48 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #19409: Function jsonb_strip_nulls() changed from immutable to stable.
2026-02-16 20:19 UTC Andrew Dunstan <andrew@dunslane.net>
` Re: BUG #19409: Function jsonb_strip_nulls() changed from immutable to stable.
2026-02-17 21:25 UTC Andrew Dunstan <andrew@dunslane.net>
` Re: BUG #19409: Function jsonb_strip_nulls() changed from immutable to stable.
2026-02-17 21:55 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #19409: Function jsonb_strip_nulls() changed from immutable to stable.
2026-02-18 18:05 UTC Andrew Dunstan <andrew@dunslane.net>
` Re: BUG #19409: Function jsonb_strip_nulls() changed from immutable to stable.
2026-02-18 19:18 UTC Tom Lane <tgl@sss.pgh.pa.us>
[10+ messages in thread]
17.8 standby crashes during WAL replay from 17.5 primary: "could not access status of transaction"
2026-02-13 20:31 UTC Sebastian Webber <sebastian@swebber.me>
` Re: 17.8 standby crashes during WAL replay from 17.5 primary: "could not access status of transaction"
2026-02-14 09:05 UTC Michael Banck <mbanck@gmx.net>
` Re: 17.8 standby crashes during WAL replay from 17.5 primary: "could not access status of transaction"
2026-02-14 11:42 UTC Heikki Linnakangas <hlinnaka@iki.fi>
` Re: 17.8 standby crashes during WAL replay from 17.5 primary: "could not access status of transaction"
2026-02-14 16:18 UTC Andrey Borodin <x4mmm@yandex-team.ru>
` Re: 17.8 standby crashes during WAL replay from 17.5 primary: "could not access status of transaction"
2026-02-14 17:41 UTC Andrey Borodin <x4mmm@yandex-team.ru>
` Re: 17.8 standby crashes during WAL replay from 17.5 primary: "could not access status of transaction"
2026-02-15 18:11 UTC Andrey Borodin <x4mmm@yandex-team.ru>
` Re: 17.8 standby crashes during WAL replay from 17.5 primary: "could not access status of transaction"
2026-02-16 06:45 UTC Kirill Reshke <reshkekirill@gmail.com>
` Re: 17.8 standby crashes during WAL replay from 17.5 primary: "could not access status of transaction"
2026-02-16 16:01 UTC Heikki Linnakangas <hlinnaka@iki.fi>
` Re: 17.8 standby crashes during WAL replay from 17.5 primary: "could not access status of transaction"
2026-02-18 08:58 UTC Andrey Borodin <x4mmm@yandex-team.ru>
[9+ messages in thread]
BUG #19095: Test if function exit() is used fail when linked static
2025-10-27 07:56 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #19095: Test if function exit() is used fail when linked static
2025-10-28 03:16 UTC Michael Paquier <michael@paquier.xyz>
` Re: BUG #19095: Test if function exit() is used fail when linked static
2025-11-09 08:33 UTC Torsten Rupp <torsten.rupp@gmx.net>
` Re: BUG #19095: Test if function exit() is used fail when linked static
2025-11-12 05:53 UTC BharatDB <bharatdbpg@gmail.com>
` Fwd: BUG #19095: Test if function exit() is used fail when linked static
2025-11-12 05:54 UTC BharatDB <bharatdbpg@gmail.com>
` Re: BUG #19095: Test if function exit() is used fail when linked static
2025-11-12 06:38 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #19095: Test if function exit() is used fail when linked static
2025-11-12 08:13 UTC Daniel Gustafsson <daniel@yesql.se>
` Re: BUG #19095: Test if function exit() is used fail when linked static
2025-11-12 08:15 UTC Michael Paquier <michael@paquier.xyz>
` Re: BUG #19095: Test if function exit() is used fail when linked static
2025-11-14 12:11 UTC Daniel Gustafsson <daniel@yesql.se>
` Re: BUG #19095: Test if function exit() is used fail when linked static
2025-11-14 14:01 UTC Andres Freund <andres@anarazel.de>
` Re: BUG #19095: Test if function exit() is used fail when linked static
2025-11-14 14:40 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #19095: Test if function exit() is used fail when linked static
2025-11-19 09:08 UTC BharatDB <bharatdbpg@gmail.com>
` Re: BUG #19095: Test if function exit() is used fail when linked static
2025-11-19 12:29 UTC BharatDB <bharatdbpg@gmail.com>
` Re: BUG #19095: Test if function exit() is used fail when linked static
2025-11-19 13:17 UTC Nazir Bilal Yavuz <byavuz81@gmail.com>
` Re: BUG #19095: Test if function exit() is used fail when linked static
2025-11-24 11:04 UTC Nazir Bilal Yavuz <byavuz81@gmail.com>
` Re: BUG #19095: Test if function exit() is used fail when linked static
2025-11-24 21:43 UTC Michael Paquier <michael@paquier.xyz>
` Re: BUG #19095: Test if function exit() is used fail when linked static
2025-11-25 09:11 UTC VASUKI M <vasukim1992002@gmail.com>
` Re: BUG #19095: Test if function exit() is used fail when linked static
2025-11-25 10:07 UTC Nazir Bilal Yavuz <byavuz81@gmail.com>
` Re: BUG #19095: Test if function exit() is used fail when linked static
2025-11-25 10:51 UTC Daniel Gustafsson <daniel@yesql.se>
` Re: BUG #19095: Test if function exit() is used fail when linked static
2025-11-26 03:43 UTC Michael Paquier <michael@paquier.xyz>
` Re: BUG #19095: Test if function exit() is used fail when linked static
2025-12-01 04:57 UTC VASUKI M <vasukim1992002@gmail.com>
` Re: BUG #19095: Test if function exit() is used fail when linked static
2025-12-03 11:59 UTC VASUKI M <vasukim1992002@gmail.com>
` Re: BUG #19095: Test if function exit() is used fail when linked static
2025-12-03 23:33 UTC Daniel Gustafsson <daniel@yesql.se>
` Re: BUG #19095: Test if function exit() is used fail when linked static
2025-12-04 00:32 UTC Michael Paquier <michael@paquier.xyz>
` Re: BUG #19095: Test if function exit() is used fail when linked static
2025-12-04 11:08 UTC VASUKI M <vasukim1992002@gmail.com>
` Re: BUG #19095: Test if function exit() is used fail when linked static
2025-12-05 00:41 UTC Michael Paquier <michael@paquier.xyz>
` Re: BUG #19095: Test if function exit() is used fail when linked static
2025-12-08 04:41 UTC VASUKI M <vasukim1992002@gmail.com>
` Re: BUG #19095: Test if function exit() is used fail when linked static
2025-12-09 04:16 UTC Michael Paquier <michael@paquier.xyz>
` Re: BUG #19095: Test if function exit() is used fail when linked static
2025-12-09 06:10 UTC Peter Eisentraut <peter@eisentraut.org>
` Re: BUG #19095: Test if function exit() is used fail when linked static
2025-12-09 06:26 UTC Michael Paquier <michael@paquier.xyz>
` Re: BUG #19095: Test if function exit() is used fail when linked static
2025-12-09 10:23 UTC VASUKI M <vasukim1992002@gmail.com>
` Re: BUG #19095: Test if function exit() is used fail when linked static
2025-12-09 12:47 UTC Bilal Yavuz <byavuz81@gmail.com>
` Re: BUG #19095: Test if function exit() is used fail when linked static
2025-12-09 23:11 UTC Michael Paquier <michael@paquier.xyz>
` Re: BUG #19095: Test if function exit() is used fail when linked static
2025-12-10 05:14 UTC Michael Paquier <michael@paquier.xyz>
` Re: BUG #19095: Test if function exit() is used fail when linked static
2026-02-17 12:04 UTC Nazir Bilal Yavuz <byavuz81@gmail.com>
` Re: BUG #19095: Test if function exit() is used fail when linked static
2026-02-18 04:19 UTC VASUKI M <vasukim1992002@gmail.com>
` Re: BUG #19095: Test if function exit() is used fail when linked static
2026-02-18 08:19 UTC Michael Paquier <michael@paquier.xyz>
[37+ messages in thread]
BUG #19411: libpq 16.x exhibits a memory leak when connections are repeatedly created and destroyed
2026-02-16 20:44 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #19411: libpq 16.x exhibits a memory leak when connections are repeatedly created and destroyed
2026-02-17 17:01 UTC Tom Lane <tgl@sss.pgh.pa.us>
` RE: BUG #19411: libpq 16.x exhibits a memory leak when connections are repeatedly created and destroyed
2026-02-17 17:54 UTC Matt Carter <Matt.Carter@twosigma.com>
` Re: BUG #19411: libpq 16.x exhibits a memory leak when connections are repeatedly created and destroyed
2026-02-17 18:47 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #19411: libpq 16.x exhibits a memory leak when connections are repeatedly created and destroyed
2026-02-17 19:45 UTC Andres Freund <andres@anarazel.de>
` RE: BUG #19411: libpq 16.x exhibits a memory leak when connections are repeatedly created and destroyed
2026-02-17 20:54 UTC Matt Carter <Matt.Carter@twosigma.com>
` RE: BUG #19411: libpq 16.x exhibits a memory leak when connections are repeatedly created and destroyed
2026-02-17 23:12 UTC Matt Carter <Matt.Carter@twosigma.com>
[7+ messages in thread]
BUG #19406: substring(text) fails on valid UTF-8 toasted value in PostgreSQL 15.16
2026-02-13 07:46 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #19406: substring(text) fails on valid UTF-8 toasted value in PostgreSQL 15.16
2026-02-13 17:27 UTC Noah Misch <noah@leadboat.com>
` Re: BUG #19406: substring(text) fails on valid UTF-8 toasted value in PostgreSQL 15.16
2026-02-13 21:58 UTC Thomas Munro <thomas.munro@gmail.com>
` Re: BUG #19406: substring(text) fails on valid UTF-8 toasted value in PostgreSQL 15.16
2026-02-13 22:48 UTC Noah Misch <noah@leadboat.com>
` Re: BUG #19406: substring(text) fails on valid UTF-8 toasted value in PostgreSQL 15.16
2026-02-14 00:21 UTC Noah Misch <noah@leadboat.com>
` Re: BUG #19406: substring(text) fails on valid UTF-8 toasted value in PostgreSQL 15.16
2026-02-14 05:38 UTC Noah Misch <noah@leadboat.com>
` Re: BUG #19406: substring(text) fails on valid UTF-8 toasted value in PostgreSQL 15.16
2026-02-14 08:15 UTC Thomas Munro <thomas.munro@gmail.com>
` Re: BUG #19406: substring(text) fails on valid UTF-8 toasted value in PostgreSQL 15.16
2026-02-14 19:07 UTC Thomas Munro <thomas.munro@gmail.com>
` Re: BUG #19406: substring(text) fails on valid UTF-8 toasted value in PostgreSQL 15.16
2026-02-14 19:33 UTC Noah Misch <noah@leadboat.com>
` Re: BUG #19406: substring(text) fails on valid UTF-8 toasted value in PostgreSQL 15.16
2026-02-14 20:10 UTC Thomas Munro <thomas.munro@gmail.com>
` Re: BUG #19406: substring(text) fails on valid UTF-8 toasted value in PostgreSQL 15.16
2026-02-14 20:19 UTC Thomas Munro <thomas.munro@gmail.com>
` Re: BUG #19406: substring(text) fails on valid UTF-8 toasted value in PostgreSQL 15.16
2026-02-14 22:46 UTC Noah Misch <noah@leadboat.com>
` Re: BUG #19406: substring(text) fails on valid UTF-8 toasted value in PostgreSQL 15.16
2026-02-16 18:21 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #19406: substring(text) fails on valid UTF-8 toasted value in PostgreSQL 15.16
2026-02-17 04:20 UTC Noah Misch <noah@leadboat.com>
` Re: BUG #19406: substring(text) fails on valid UTF-8 toasted value in PostgreSQL 15.16
2026-02-17 18:15 UTC Noah Misch <noah@leadboat.com>
[15+ messages in thread]
BUG #19410: Cannot ser client_encoding
2026-02-15 01:53 UTC PG Bug reporting form <noreply@postgresql.org>
` BUG #19410: Cannot ser client_encoding
2026-02-15 14:55 UTC David G. Johnston <david.g.johnston@gmail.com>
` Re: BUG #19410: Cannot ser client_encoding
2026-02-15 15:10 UTC Tom Lane <tgl@sss.pgh.pa.us>
[3+ messages in thread]
BUG #19407: pg_dump : DROP RULE creates forward references
2026-02-13 09:02 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #19407: pg_dump : DROP RULE creates forward references
2026-02-13 21:00 UTC Nathan Bossart <nathandbossart@gmail.com>
` Re: BUG #19407: pg_dump : DROP RULE creates forward references
2026-02-13 22:16 UTC Nathan Bossart <nathandbossart@gmail.com>
` Re: BUG #19407: pg_dump : DROP RULE creates forward references
2026-02-14 01:11 UTC Tom Lane <tgl@sss.pgh.pa.us>
[4+ messages in thread]
BUG #19408: Bad plan for UNION ALL subquery with outer WHERE, ORDER BY, LIMIT, and separate indexes
2026-02-13 19:05 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #19408: Bad plan for UNION ALL subquery with outer WHERE, ORDER BY, LIMIT, and separate indexes
2026-02-13 23:36 UTC Tom Lane <tgl@sss.pgh.pa.us>
[2+ messages in thread]
BUG #19403: psql fails when trying to import a file that
2026-02-12 12:24 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #19403: psql fails when trying to import a file that
2026-02-12 17:17 UTC Tom Lane <tgl@sss.pgh.pa.us>
[2+ messages in thread]
BUG #19402: CREATE TABLE IF NOT EXISTS raises DuplicateTable error under concurrent partition creation
2026-02-12 08:16 UTC PG Bug reporting form <noreply@postgresql.org>
BUG #15983: pg_dump converts CRLF to LF
2019-08-29 14:07 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #15983: pg_dump converts CRLF to LF
2019-08-29 14:33 UTC Tom Lane <tgl@sss.pgh.pa.us>
` [PATCH v1 1/1] basic_archive: Allow archive directory to be missing at startup.
2026-02-11 21:10 UTC Nathan Bossart <nathan@postgresql.org>
[3+ messages in thread]
BUG #19401: Inconsistent predicate evaluation with derived table vs direct query involving NULL
2026-02-11 15:57 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #19401: Inconsistent predicate evaluation with derived table vs direct query involving NULL
2026-02-11 16:43 UTC Tom Lane <tgl@sss.pgh.pa.us>
[2+ messages in thread]
BUG #19400: Memory leak in checkpointer and startup processes on PostgreSQL 18
2026-02-10 15:28 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #19400: Memory leak in checkpointer and startup processes on PostgreSQL 18
2026-02-10 19:58 UTC Andres Freund <andres@anarazel.de>
` Re: BUG #19400: Memory leak in checkpointer and startup processes on PostgreSQL 18
2026-02-11 09:56 UTC Raphaël Perissat <raphael@atmotrack.fr>
[3+ messages in thread]
Possibly a bug
2026-02-09 12:41 UTC Анатолий <anatoly@email.su>
` Re: Possibly a bug
2026-02-09 16:14 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: Possibly a bug
2026-02-09 23:51 UTC surya poondla <suryapoondla4@gmail.com>
` Re: Possibly a bug
2026-02-10 02:11 UTC jian he <jian.universality@gmail.com>
` Re: Possibly a bug
2026-02-10 21:51 UTC surya poondla <suryapoondla4@gmail.com>
` Re: Possibly a bug
2026-02-10 22:34 UTC Tom Lane <tgl@sss.pgh.pa.us>
[6+ messages in thread]
BUG #19399: Cached plans retain outdated parameter information
2026-02-10 09:16 UTC PG Bug reporting form <noreply@postgresql.org>
[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