pg.ddx.io  pgsql-bugs@postgresql.org mailing list archive  
help / color / mirror / Atom feed
BUG #18921: The larger the value of max_parallel_workers_per_gather, the longer the SQL execution time.
  2025-05-10 10:10 UTC  PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18921: The larger the value of max_parallel_workers_per_gather, the longer the SQL execution time.
  2025-05-11 08:32 UTC  Dilip Kumar <dilipbalaut@gmail.com>
  [2+ messages in thread]

AW: BUG #18918: cron.schedule_in_database ERROR: must be superuser to create a job for another role
  2025-05-09 09:52 UTC  Silvan Laube <silvanlaube@hotmail.com>

BUG #18919: Source archives in ftp/source/v17.5 are missing
  2025-05-08 16:17 UTC  PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18919: Source archives in ftp/source/v17.5 are missing
  2025-05-08 19:21 UTC  Álvaro Herrera <alvherre@kurilemu.de>
  [2+ messages in thread]

BUG #18918: cron.schedule_in_database ERROR: must be superuser to create a job for another role
  2025-05-08 15:54 UTC  PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18918: cron.schedule_in_database ERROR: must be superuser to create a job for another role
  2025-05-08 18:17 UTC  David G. Johnston <david.g.johnston@gmail.com>
  [2+ messages in thread]

Re: Issue attaching a table to a partitioned table with an auto-referenced foreign key
  2025-05-01 12:14 UTC  Alvaro Herrera <alvherre@alvh.no-ip.org>
` Re: Issue attaching a table to a partitioned table with an auto-referenced foreign key
  2025-05-01 15:21 UTC  Tender Wang <tndrwang@gmail.com>
` Re: Issue attaching a table to a partitioned table with an auto-referenced foreign key
  2025-05-03 13:09 UTC  Alvaro Herrera <alvherre@kurilemu.de>
` Re: Issue attaching a table to a partitioned table with an auto-referenced foreign key
  2025-05-08 17:14 UTC  Matthew Gabeler-Lee <fastcat@gmail.com>
` Re: Issue attaching a table to a partitioned table with an auto-referenced foreign key
  2025-05-08 17:35 UTC  Alvaro Herrera <alvherre@kurilemu.de>
  [5+ messages in thread]

BUG #18911: Bug in the command INHERITS.
  2025-05-05 14:30 UTC  PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18911: Bug in the command INHERITS.
  2025-05-05 15:30 UTC  David G. Johnston <david.g.johnston@gmail.com>
` Re: BUG #18911: Bug in the command INHERITS.
  2025-05-06 15:39 UTC  David G. Johnston <david.g.johnston@gmail.com>
` Re: BUG #18911: Bug in the command INHERITS.
  2025-05-07 07:00 UTC  M. BROUSSE <bm16ch24f@gmail.com>
` Re: BUG #18911: Bug in the command INHERITS.
  2025-05-07 13:33 UTC  David G. Johnston <david.g.johnston@gmail.com>
` Re: BUG #18911: Bug in the command INHERITS.
  2025-05-07 14:59 UTC  Álvaro Herrera <alvherre@kurilemu.de>
` Re: BUG #18911: Bug in the command INHERITS.
  2025-05-08 11:27 UTC  M. BROUSSE <bm16ch24f@gmail.com>
  [7+ messages in thread]

BUG #18902: TRAP:: failed Assert("!is_sorted") in File: "createplan.c"
  2025-04-23 04:48 UTC  PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18902: TRAP:: failed Assert("!is_sorted") in File: "createplan.c"
  2025-04-23 11:03 UTC  Tender Wang <tndrwang@gmail.com>
` Re: BUG #18902: TRAP:: failed Assert("!is_sorted") in File: "createplan.c"
  2025-04-23 11:47 UTC  Tender Wang <tndrwang@gmail.com>
` Re: BUG #18902: TRAP:: failed Assert("!is_sorted") in File: "createplan.c"
  2025-04-24 08:40 UTC  Richard Guo <guofenglinux@gmail.com>
` Re: BUG #18902: TRAP:: failed Assert("!is_sorted") in File: "createplan.c"
  2025-04-24 09:20 UTC  Richard Guo <guofenglinux@gmail.com>
` Re: BUG #18902: TRAP:: failed Assert("!is_sorted") in File: "createplan.c"
  2025-04-24 09:43 UTC  Richard Guo <guofenglinux@gmail.com>
` Re: BUG #18902: TRAP:: failed Assert("!is_sorted") in File: "createplan.c"
  2025-04-24 10:58 UTC  David Rowley <dgrowleyml@gmail.com>
` Re: BUG #18902: TRAP:: failed Assert("!is_sorted") in File: "createplan.c"
  2025-04-24 13:29 UTC  Tender Wang <tndrwang@gmail.com>
` Re: BUG #18902: TRAP:: failed Assert("!is_sorted") in File: "createplan.c"
  2025-04-25 02:16 UTC  Richard Guo <guofenglinux@gmail.com>
` Re: BUG #18902: TRAP:: failed Assert("!is_sorted") in File: "createplan.c"
  2025-04-27 00:14 UTC  David Rowley <dgrowleyml@gmail.com>
` Re: BUG #18902: TRAP:: failed Assert("!is_sorted") in File: "createplan.c"
  2025-05-02 07:03 UTC  Richard Guo <guofenglinux@gmail.com>
` Re: BUG #18902: TRAP:: failed Assert("!is_sorted") in File: "createplan.c"
  2025-05-03 01:50 UTC  Tender Wang <tndrwang@gmail.com>
` Re: BUG #18902: TRAP:: failed Assert("!is_sorted") in File: "createplan.c"
  2025-05-08 10:26 UTC  Richard Guo <guofenglinux@gmail.com>
` Re: BUG #18902: TRAP:: failed Assert("!is_sorted") in File: "createplan.c"
  2025-05-08 10:28 UTC  Richard Guo <guofenglinux@gmail.com>
  [14+ messages in thread]

BUG #18917: "Foreign key constraint drop fails with 'column is not in index' unless pg_constraint is queried
  2025-05-08 01:23 UTC  PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18917: "Foreign key constraint drop fails with 'column is not in index' unless pg_constraint is queried
  2025-05-08 01:50 UTC  Tom Lane <tgl@sss.pgh.pa.us>
  [2+ messages in thread]

BUG #18916: alter table ... set (n_distinct=) completely ignored on partition head and/or individual partitions
  2025-05-07 21:18 UTC  PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18916: alter table ... set (n_distinct=) completely ignored on partition head and/or individual partitions
  2025-05-07 22:49 UTC  David Rowley <dgrowleyml@gmail.com>
  [2+ messages in thread]

Different behavior between v15 and v17 using WITH CTE
  2025-05-07 18:58 UTC  marcos sicat <marcos.sicat@atlasifs.com>
` Re: Different behavior between v15 and v17 using WITH CTE
  2025-05-07 19:03 UTC  David G. Johnston <david.g.johnston@gmail.com>
` Re: Different behavior between v15 and v17 using WITH CTE
  2025-05-07 19:07 UTC  marcos sicat <marcos.sicat@atlasifs.com>
  [3+ messages in thread]

BUG #18913: pgdg-redhat-repo-42.0-52PGDG.noarch: Cannot download, all mirrors were already tried without succes
  2025-05-07 02:01 UTC  PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18913: pgdg-redhat-repo-42.0-52PGDG.noarch: Cannot download, all mirrors were already tried without succes
  2025-05-07 16:26 UTC  Devrim Gündüz <devrim@gunduz.org>
  [2+ messages in thread]

BUG #18915: pgdg-redhat-repo-42.0-51PGDG.noarch package not available in postgres repo
  2025-05-07 13:14 UTC  PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18915: pgdg-redhat-repo-42.0-51PGDG.noarch package not available in postgres repo
  2025-05-07 16:25 UTC  Devrim Gündüz <devrim@gunduz.org>
  [2+ messages in thread]

BUG #18914: REDUNDANT_COMPARISON.ALWAYS_FALSE Redundant comparison '0' > 'nb' (0 > {4, 16}) is always false
  2025-05-07 08:48 UTC  PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18914: REDUNDANT_COMPARISON.ALWAYS_FALSE Redundant comparison '0' > 'nb' (0 > {4, 16}) is always false
  2025-05-07 10:34 UTC  David Rowley <dgrowleyml@gmail.com>
` Re: BUG #18914: REDUNDANT_COMPARISON.ALWAYS_FALSE Redundant comparison '0' > 'nb' (0 > {4, 16}) is always false
  2025-05-07 10:35 UTC  Daniel Gustafsson <daniel@yesql.se>
  [3+ messages in thread]

BUG #18912: TRAP: failed Assert("tag.spcOid != GLOBALTABLESPACE_OID"), File: "bufmgr.c", Line: 4165, PID: 2115
  2025-05-05 22:01 UTC  PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18912: TRAP: failed Assert("tag.spcOid != GLOBALTABLESPACE_OID"), File: "bufmgr.c", Line: 4165, PID: 2115
  2025-05-06 00:31 UTC  Noah Misch <noah@leadboat.com>
` Re: BUG #18912: TRAP: failed Assert("tag.spcOid != GLOBALTABLESPACE_OID"), File: "bufmgr.c", Line: 4165, PID: 2115
  2025-05-06 04:52 UTC  Masahiko Sawada <sawada.mshk@gmail.com>
  [3+ messages in thread]

BUG #18910: DEREF_OF_NULL.RET Pointer, returned from function 'palloc0' at simplehash.h:1080, may be NULL
  2025-05-05 08:00 UTC  PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18910: DEREF_OF_NULL.RET Pointer, returned from function 'palloc0' at simplehash.h:1080, may be NULL
  2025-05-05 14:43 UTC  Tom Lane <tgl@sss.pgh.pa.us>
  [2+ messages in thread]

BUG #18909: Query creates millions of temporary files and stalls
  2025-05-02 18:45 UTC  PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18909: Query creates millions of temporary files and stalls
  2025-05-02 22:12 UTC  Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #18909: Query creates millions of temporary files and stalls
  2025-05-02 22:44 UTC  Sergey Koposov <Sergey.Koposov@ed.ac.uk>
` Re: BUG #18909: Query creates millions of temporary files and stalls
  2025-05-03 16:11 UTC  Sergey Koposov <Sergey.Koposov@ed.ac.uk>
` Re: BUG #18909: Query creates millions of temporary files and stalls
  2025-05-03 16:27 UTC  Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #18909: Query creates millions of temporary files and stalls
  2025-05-03 16:52 UTC  Sergey Koposov <Sergey.Koposov@ed.ac.uk>
` Re: BUG #18909: Query creates millions of temporary files and stalls
  2025-05-03 17:56 UTC  Andrei Lepikhov <lepihov@gmail.com>
` Re: BUG #18909: Query creates millions of temporary files and stalls
  2025-05-03 19:20 UTC  Sergey Koposov <Sergey.Koposov@ed.ac.uk>
` Re: BUG #18909: Query creates millions of temporary files and stalls
  2025-05-03 21:50 UTC  Sergey Koposov <Sergey.Koposov@ed.ac.uk>
` Re: BUG #18909: Query creates millions of temporary files and stalls
  2025-05-03 22:03 UTC  Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #18909: Query creates millions of temporary files and stalls
  2025-05-03 22:30 UTC  Sergey Koposov <Sergey.Koposov@ed.ac.uk>
` Re: BUG #18909: Query creates millions of temporary files and stalls
  2025-05-03 22:47 UTC  Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #18909: Query creates millions of temporary files and stalls
  2025-05-03 23:05 UTC  Sergey Koposov <Sergey.Koposov@ed.ac.uk>
` Re: BUG #18909: Query creates millions of temporary files and stalls
  2025-05-04 07:52 UTC  Andrei Lepikhov <lepihov@gmail.com>
` Re: BUG #18909: Query creates millions of temporary files and stalls
  2025-05-04 11:45 UTC  Sergey Koposov <Sergey.Koposov@ed.ac.uk>
` Re: BUG #18909: Query creates millions of temporary files and stalls
  2025-05-04 12:13 UTC  Andrei Lepikhov <lepihov@gmail.com>
` Re: BUG #18909: Query creates millions of temporary files and stalls
  2025-05-04 12:35 UTC  Sergey Koposov <Sergey.Koposov@ed.ac.uk>
  [17+ messages in thread]

Planner does not use btree index for LIKE 'prefix%' on text column, but does for equivalent range query (PostgreSQL 17.4)
  2025-05-03 16:50 UTC  Abdullah DURSUN <adursuns@gmail.com>
` Re: Planner does not use btree index for LIKE 'prefix%' on text column, but does for equivalent range query (PostgreSQL 17.4)
  2025-05-03 20:04 UTC  Tom Lane <tgl@sss.pgh.pa.us>
  [2+ messages in thread]

BUG #18741: Detaching a partition referencing a partitioned table fails with a trigger-related error
  2024-12-08 12:00 UTC  PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18741: Detaching a partition referencing a partitioned table fails with a trigger-related error
  2024-12-09 02:56 UTC  Tender Wang <tndrwang@gmail.com>
` Re: BUG #18741: Detaching a partition referencing a partitioned table fails with a trigger-related error
  2024-12-31 05:00 UTC  jian he <jian.universality@gmail.com>
` Re: BUG #18741: Detaching a partition referencing a partitioned table fails with a trigger-related error
  2025-05-03 01:22 UTC  Tender Wang <tndrwang@gmail.com>
` Re: BUG #18741: Detaching a partition referencing a partitioned table fails with a trigger-related error
  2025-05-03 05:00 UTC  Alexander Lakhin <exclusion@gmail.com>
  [5+ messages in thread]

[PATCH] Fix self-referencing foreign keys on partitioned tables
  2025-05-01 11:14 UTC  Álvaro Herrera <alvherre@kurilemu.de>

Postgres 17.4 is much slower than Postgres 15.12 using RECURSIVE
  2025-04-27 20:51 UTC  marcos sicat <marcos.sicat@atlasifs.com>
` Re: Postgres 17.4 is much slower than Postgres 15.12 using RECURSIVE
  2025-04-28 06:17 UTC  Pavel Stehule <pavel.stehule@gmail.com>
` Re: Postgres 17.4 is much slower than Postgres 15.12 using RECURSIVE
  2025-04-28 13:05 UTC  marcos sicat <marcos.sicat@atlasifs.com>
` Re: Postgres 17.4 is much slower than Postgres 15.12 using RECURSIVE
  2025-04-28 13:59 UTC  Tom Lane <tgl@sss.pgh.pa.us>
` Re: Postgres 17.4 is much slower than Postgres 15.12 using RECURSIVE
  2025-04-28 21:53 UTC  marcos sicat <marcos.sicat@atlasifs.com>
` Re: Postgres 17.4 is much slower than Postgres 15.12 using RECURSIVE
  2025-04-29 05:00 UTC  Pavel Stehule <pavel.stehule@gmail.com>
` Re: Postgres 17.4 is much slower than Postgres 15.12 using RECURSIVE
  2025-04-30 21:43 UTC  marcos sicat <marcos.sicat@atlasifs.com>
` Re: Postgres 17.4 is much slower than Postgres 15.12 using RECURSIVE
  2025-04-30 23:16 UTC  David Rowley <dgrowleyml@gmail.com>
` Re: Postgres 17.4 is much slower than Postgres 15.12 using RECURSIVE
  2025-04-30 23:53 UTC  marcos sicat <marcos.sicat@atlasifs.com>
` Re: Postgres 17.4 is much slower than Postgres 15.12 using RECURSIVE
  2025-05-01 00:27 UTC  marcos sicat <marcos.sicat@atlasifs.com>
  [10+ messages in thread]

Doubt in reset date style
  2025-04-30 21:17 UTC  Manav Kumar <mkumar@yugabyte.com>
` Re: Doubt in reset date style
  2025-04-30 21:31 UTC  David G. Johnston <david.g.johnston@gmail.com>
` Re: Doubt in reset date style
  2025-04-30 21:56 UTC  Tom Lane <tgl@sss.pgh.pa.us>
  [3+ messages in thread]

BUG #17695: Failed Assert in logical replication snapbuild.
  2022-11-24 10:15 UTC  PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #17695: Failed Assert in logical replication snapbuild.
  2022-11-24 12:39 UTC  vignesh C <vignesh21@gmail.com>
` Re: BUG #17695: Failed Assert in logical replication snapbuild.
  2022-11-25 05:58 UTC  Masahiko Sawada <sawada.mshk@gmail.com>
` Re: BUG #17695: Failed Assert in logical replication snapbuild.
  2022-11-25 07:44 UTC  bowenshi <zxwsbg@qq.com>
` RE: BUG #17695: Failed Assert in logical replication snapbuild.
  2022-11-25 09:07 UTC  Hayato Kuroda (Fujitsu) <kuroda.hayato@fujitsu.com>
` Re: BUG #17695: Failed Assert in logical replication snapbuild.
  2022-11-25 09:56 UTC  bowenshi <zxwsbg@qq.com>
` Re: BUG #17695: Failed Assert in logical replication snapbuild.
  2022-11-28 05:07 UTC  Masahiko Sawada <sawada.mshk@gmail.com>
` Re: BUG #17695: Failed Assert in logical replication snapbuild.
  2023-03-27 11:49 UTC  Daniel Gustafsson <daniel@yesql.se>
` Re: BUG #17695: Failed Assert in logical replication snapbuild.
  2023-05-17 05:34 UTC  Masahiko Sawada <sawada.mshk@gmail.com>
` Re: BUG #17695: Failed Assert in logical replication snapbuild.
  2023-05-18 14:00 UTC  Alexander Lakhin <exclusion@gmail.com>
` Re: BUG #17695: Failed Assert in logical replication snapbuild.
  2023-05-22 00:56 UTC  Masahiko Sawada <sawada.mshk@gmail.com>
` Re: BUG #17695: Failed Assert in logical replication snapbuild.
  2023-05-23 11:00 UTC  Alexander Lakhin <exclusion@gmail.com>
` Re: BUG #17695: Failed Assert in logical replication snapbuild.
  2023-07-04 15:43 UTC  Daniel Gustafsson <daniel@yesql.se>
` Re: BUG #17695: Failed Assert in logical replication snapbuild.
  2023-07-05 01:23 UTC  Masahiko Sawada <sawada.mshk@gmail.com>
` Re: BUG #17695: Failed Assert in logical replication snapbuild.
  2023-09-19 08:15 UTC  Alexander Pyhalov <a.pyhalov@postgrespro.ru>
` Re: BUG #17695: Failed Assert in logical replication snapbuild.
  2025-04-30 18:19 UTC  Daniel Gustafsson <daniel@yesql.se>
` Re: BUG #17695: Failed Assert in logical replication snapbuild.
  2025-04-30 19:55 UTC  Masahiko Sawada <sawada.mshk@gmail.com>
  [17+ messages in thread]

BUG #18904: INTERSECT with an impossible where should eliminate both from the query plan
  2025-04-27 16:15 UTC  PG Bug reporting form <noreply@postgresql.org>
` BUG #18904: INTERSECT with an impossible where should eliminate both from the query plan
  2025-04-27 17:32 UTC  David G. Johnston <david.g.johnston@gmail.com>
` Re: BUG #18904: INTERSECT with an impossible where should eliminate both from the query plan
  2025-04-27 18:02 UTC  Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #18904: INTERSECT with an impossible where should eliminate both from the query plan
  2025-04-29 11:57 UTC  David Rowley <dgrowleyml@gmail.com>
` Re: BUG #18904: INTERSECT with an impossible where should eliminateboth from the query plan
  2025-04-29 12:13 UTC  =?utf-8?B?SmluaHVpIExhaQ==?= <jh.lai@qq.com>
` Re: BUG #18904: INTERSECT with an impossible where should eliminateboth from the query plan
  2025-04-29 12:55 UTC  David Rowley <dgrowleyml@gmail.com>
` Re: BUG #18904: INTERSECT with an impossible where should eliminateboth from the query plan
  2025-04-29 18:44 UTC  Francisco Olarte <folarte@peoplecall.com>
  [7+ messages in thread]

BUG #18905: The opposite WHERE clause intersects and is always an empty set. It should perform no action.
  2025-04-27 16:49 UTC  PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18905: The opposite WHERE clause intersects and is always an empty set. It should perform no action.
  2025-04-27 17:34 UTC  David G. Johnston <david.g.johnston@gmail.com>
` Re: BUG #18905: The opposite WHERE clause intersects and is always an empty set. It should perform no action.
  2025-04-27 17:54 UTC  =?utf-8?B?6LWW6ZSm6L6J?= <jh.lai@qq.com>
` Re: BUG #18905: The opposite WHERE clause intersects and is always an empty set. It should perform no action.
  2025-04-27 19:19 UTC  Christophe Pettus <xof@thebuild.com>
  [4+ messages in thread]

BUG #18906: EXCEPT with identical left/right queries isn't eliminated
  2025-04-27 17:05 UTC  PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18906: EXCEPT with identical left/right queries isn't eliminated
  2025-04-27 17:37 UTC  David G. Johnston <david.g.johnston@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