pg.ddx.io pgsql-bugs@postgresql.org mailing list archive
help / color / mirror / Atom feedBUG #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>
Incorrect description for "SET" abbreviation in Time Zone Appendix
2026-02-08 07:50 UTC Mohamed Medjelled <medjmohamed2001@gmail.com>
` Re: Incorrect description for "SET" abbreviation in Time Zone Appendix
2026-02-08 18:10 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: Incorrect description for "SET" abbreviation in Time Zone Appendix
2026-02-09 18:34 UTC Greg Sabino Mullane <htamfids@gmail.com>
[3+ messages in thread]
BUG #19398: Non-existent repositories are used
2026-02-09 11:33 UTC PG Bug reporting form <noreply@postgresql.org>
BUG #19395: Postgres master: undeclared function 'typeof_unqual'
2026-02-06 03:08 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #19395: Postgres master: undeclared function 'typeof_unqual'
2026-02-06 16:52 UTC Euler Taveira <euler@eulerto.com>
[2+ messages in thread]
BUG #19394: error in ecpg
2026-02-05 14:58 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #19394: error in ecpg
2026-02-05 15:31 UTC David G. Johnston <david.g.johnston@gmail.com>
[2+ messages in thread]
BUG #19392: PG_UPGRADE is non-functional on Windows
2026-02-04 02:29 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #19392: PG_UPGRADE is non-functional on Windows
2026-02-04 06:43 UTC David G. Johnston <david.g.johnston@gmail.com>
` Re: BUG #19392: PG_UPGRADE is non-functional on Windows
2026-02-04 06:50 UTC Michael Paquier <michael@paquier.xyz>
` Re: BUG #19392: PG_UPGRADE is non-functional on Windows
2026-02-04 12:32 UTC Andrew Dunstan <andrew@dunslane.net>
` RE: BUG #19392: PG_UPGRADE is non-functional on Windows
2026-02-04 21:53 UTC Jeff Laing <jeff.laing@spatialnetworx.ai>
` Re: BUG #19392: PG_UPGRADE is non-functional on Windows
2026-02-04 23:38 UTC David G. Johnston <david.g.johnston@gmail.com>
` RE: BUG #19392: PG_UPGRADE is non-functional on Windows
2026-02-05 02:57 UTC Jeff Laing <jeff.laing@spatialnetworx.ai>
` Re: BUG #19392: PG_UPGRADE is non-functional on Windows
2026-02-05 04:23 UTC Tom Lane <tgl@sss.pgh.pa.us>
[8+ messages in thread]
BUG #19351: in pg18.1,when not null exists in the table , and add constraint problem.
2025-12-10 14:51 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #19351: in pg18.1,when not null exists in the table , and add constraint problem.
2025-12-10 16:02 UTC Srinath Reddy Sadipiralla <srinath2133@gmail.com>
` Re: BUG #19351: in pg18.1,when not null exists in the table , and add constraint problem.
2025-12-10 16:40 UTC Srinath Reddy Sadipiralla <srinath2133@gmail.com>
` Re: BUG #19351: in pg18.1,when not null exists in the table , and add constraint problem.
2025-12-11 07:27 UTC Álvaro Herrera <alvherre@kurilemu.de>
` Re: BUG #19351: in pg18.1,when not null exists in the table , and add constraint problem.
2025-12-11 07:29 UTC Álvaro Herrera <alvherre@kurilemu.de>
` Re:Re: BUG #19351: in pg18.1,when not null exists in the table , and add constraint problem.
2025-12-12 10:23 UTC yanliang lei <msdnchina@163.com>
` Re: Re: BUG #19351: in pg18.1,when not null exists in the table , and add constraint problem.
2025-12-12 15:01 UTC Álvaro Herrera <alvherre@kurilemu.de>
` Re:Re: Re: BUG #19351: in pg18.1,when not null exists in the table , and add constraint problem.
2025-12-13 04:15 UTC yanliang lei <msdnchina@163.com>
` Re: Re: Re: BUG #19351: in pg18.1,when not null exists in the table , and add constraint problem.
2025-12-13 12:44 UTC Álvaro Herrera <alvherre@kurilemu.de>
` Re: Re: Re: BUG #19351: in pg18.1,when not null exists in the table , and add constraint problem.
2025-12-14 17:00 UTC Srinath Reddy Sadipiralla <srinath2133@gmail.com>
` Re: Re: Re: BUG #19351: in pg18.1,when not null exists in the table , and add constraint problem.
2026-01-26 11:45 UTC Srinath Reddy Sadipiralla <srinath2133@gmail.com>
` Re: Re: Re: BUG #19351: in pg18.1,when not null exists in the table , and add constraint problem.
2026-01-26 14:33 UTC Álvaro Herrera <alvherre@kurilemu.de>
` Re: Re: Re: BUG #19351: in pg18.1,when not null exists in the table , and add constraint problem.
2026-01-26 15:34 UTC Srinath Reddy Sadipiralla <srinath2133@gmail.com>
` Re: Re: Re: BUG #19351: in pg18.1,when not null exists in the table , and add constraint problem.
2026-02-01 12:19 UTC Srinath Reddy Sadipiralla <srinath2133@gmail.com>
` Re: Re: Re: BUG #19351: in pg18.1,when not null exists in the table , and add constraint problem.
2026-02-02 19:22 UTC Álvaro Herrera <alvherre@kurilemu.de>
` Re: Re: Re: BUG #19351: in pg18.1,when not null exists in the table , and add constraint problem.
2026-02-03 11:40 UTC Álvaro Herrera <alvherre@kurilemu.de>
[16+ messages in thread]
BUG #19391: pg_ctl: the PID file "/xxxx/postmaster.pid" is empty
2026-01-30 15:59 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #19391: pg_ctl: the PID file "/xxxx/postmaster.pid" is empty
2026-01-31 00:54 UTC Euler Taveira <euler@eulerto.com>
` Re: BUG #19391: pg_ctl: the PID file "/xxxx/postmaster.pid" is empty
2026-01-31 01:27 UTC Dmitry Kovalenko <dmitry.lipetsk@gmail.com>
` Re: BUG #19391: pg_ctl: the PID file "/xxxx/postmaster.pid" is empty
2026-01-31 01:52 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #19391: pg_ctl: the PID file "/xxxx/postmaster.pid" is empty
2026-02-03 09:36 UTC Dmitry Kovalenko <d.kovalenko@postgrespro.ru>
[5+ messages in thread]
[PATCH v3] Reject ADD CONSTRAINT NOT NULL if name mismatches existing constraint
2026-02-02 19:19 UTC Álvaro Herrera <alvherre@kurilemu.de>
Function not found while creating partial index
2026-02-01 18:56 UTC Chris Hanks <christopher.m.hanks@gmail.com>
` Re: Function not found while creating partial index
2026-02-02 12:22 UTC Laurenz Albe <laurenz.albe@cybertec.at>
[2+ messages in thread]
BUG #19390: Defects in the test case partition_merge
2026-01-28 09:54 UTC PG Bug reporting form <noreply@postgresql.org>
BUG #19387: About Response time delay.
2026-01-23 08:59 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #19387: About Response time delay.
2026-01-23 15:16 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #19387: About Response time delay.
2026-01-26 16:51 UTC Bruce Momjian <bruce@momjian.us>
[3+ messages in thread]
BUG #19389: pg_dump output differs after setting schema comment to NULL
2026-01-25 16:28 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #19389: pg_dump output differs after setting schema comment to NULL
2026-01-25 18:46 UTC Tom Lane <tgl@sss.pgh.pa.us>
[2+ messages in thread]
pg_restore: fails to restore post-data items due to circular FK deadlock
2024-05-30 10:58 UTC vaibhave postgres <postgresvaibhave@gmail.com>
` Re: pg_restore: fails to restore post-data items due to circular FK deadlock
2024-05-30 18:29 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: pg_restore: fails to restore post-data items due to circular FK deadlock
2026-01-25 10:54 UTC vaibhave postgres <postgresvaibhave@gmail.com>
[3+ messages in thread]
BUG #19384: Server crash at textout
2026-01-20 05:11 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #19384: Server crash at textout
2026-01-20 11:15 UTC Rahila Syed <rahilasyed90@gmail.com>
` Re: BUG #19384: Server crash at textout
2026-01-20 15:03 UTC Pierre Forstmann <pierre.forstmann@gmail.com>
` Re: BUG #19384: Server crash at textout
2026-01-25 10:47 UTC vaibhave postgres <postgresvaibhave@gmail.com>
[4+ messages in thread]
BUG #19380: Transition table in AFTER INSERT trigger misses rows from MERGE when used with INSERT in a CTE
2026-01-19 19:26 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #19380: Transition table in AFTER INSERT trigger misses rows from MERGE when used with INSERT in a CTE
2026-01-20 15:59 UTC Dean Rasheed <dean.a.rasheed@gmail.com>
` Re: BUG #19380: Transition table in AFTER INSERT trigger misses rows from MERGE when used with INSERT in a CTE
2026-01-20 17:21 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #19380: Transition table in AFTER INSERT trigger misses rows from MERGE when used with INSERT in a CTE
2026-01-20 18:00 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #19380: Transition table in AFTER INSERT trigger misses rows from MERGE when used with INSERT in a CTE
2026-01-21 11:20 UTC Dean Rasheed <dean.a.rasheed@gmail.com>
` Re: BUG #19380: Transition table in AFTER INSERT trigger misses rows from MERGE when used with INSERT in a CTE
2026-01-24 11:48 UTC Dean Rasheed <dean.a.rasheed@gmail.com>
` Re: BUG #19380: Transition table in AFTER INSERT trigger misses rows from MERGE when used with INSERT in a CTE
2026-01-24 15:58 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #19380: Transition table in AFTER INSERT trigger misses rows from MERGE when used with INSERT in a CTE
2026-01-24 17:03 UTC Andres Freund <andres@anarazel.de>
` Re: BUG #19380: Transition table in AFTER INSERT trigger misses rows from MERGE when used with INSERT in a CTE
2026-01-24 17:27 UTC Tom Lane <tgl@sss.pgh.pa.us>
[9+ messages in thread]
BUG #19388: Failing to connect to postgres with EACCES error
2026-01-23 13:37 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #19388: Failing to connect to postgres with EACCES error
2026-01-23 15:35 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #19388: Failing to connect to postgres with EACCES error
2026-01-23 20:01 UTC Jacob Champion <jacob.champion@enterprisedb.com>
` Re: BUG #19388: Failing to connect to postgres with EACCES error
2026-01-23 20:31 UTC Tom Lane <tgl@sss.pgh.pa.us>
[4+ messages in thread]
BUG #19364: Repository not updating
2025-12-26 21:10 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #19364: Repository not updating
2026-01-23 06:53 UTC VASUKI M <vasukianand0119@gmail.com>
[2+ 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