pg.ddx.io pgsql-bugs@postgresql.org mailing list archive
help / color / mirror / Atom feedBUG #19068: postgresql-server-dev-17 from apt.postgresql.org installs libpq-int.h for 18 version
2025-10-02 11:08 UTC PG Bug reporting form <noreply@postgresql.org>
IN List operator , where list of values are over a number of lines
2025-10-01 15:12 UTC White, Ian Keith <Ian.White@ncratleos.com>
` Re: IN List operator , where list of values are over a number of lines
2025-10-01 18:16 UTC Pavel Stehule <pavel.stehule@gmail.com>
` RE: IN List operator , where list of values are over a number of lines
2025-10-02 08:32 UTC White, Ian Keith <Ian.White@ncratleos.com>
[3+ messages in thread]
BUG #15985: Hhhhhhh
2019-08-30 20:08 UTC PG Bug reporting form <noreply@postgresql.org>
` [PATCH] Update vacrel->dead_items alias ptr to point to the shared TidStore in parallel_vacuum after reallocation of shared TidStore.
2025-10-01 10:54 UTC Kevin Oommen Anish <kevin.o@zohocorp.com>
[2+ messages in thread]
Potential bug: Enforcing/not enforcing a CHECK constraint fails on an empty table
2025-09-30 08:56 UTC Erki Eessaar <erki.eessaar@taltech.ee>
` Re: Potential bug: Enforcing/not enforcing a CHECK constraint fails on an empty table
2025-09-30 11:36 UTC David Rowley <dgrowleyml@gmail.com>
` Re: Potential bug: Enforcing/not enforcing a CHECK constraint fails on an empty table
2025-09-30 12:12 UTC Erki Eessaar <erki.eessaar@taltech.ee>
` Re: Potential bug: Enforcing/not enforcing a CHECK constraint fails on an empty table
2025-10-01 05:24 UTC David Rowley <dgrowleyml@gmail.com>
` Re: Potential bug: Enforcing/not enforcing a CHECK constraint fails on an empty table
2025-10-01 09:34 UTC Erki Eessaar <erki.eessaar@taltech.ee>
[5+ messages in thread]
Revoke role membership does not remove cascade privileges
2025-10-01 09:32 UTC Virender Singla <virender.cse@gmail.com>
Cast to regrole on a literal string in a PL/pgSQL function
2025-09-29 12:36 UTC LEMAIRE Leslie (Chargée de mission) - SG/DNUM/UNI/DRC <leslie.lemaire@developpement-durable.gouv.fr>
` Re: Cast to regrole on a literal string in a PL/pgSQL function
2025-09-29 17:34 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: Cast to regrole on a literal string in a PL/pgSQL function
2025-09-29 22:25 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: Cast to regrole on a literal string in a PL/pgSQL function
2025-09-30 09:25 UTC LEMAIRE Leslie (Chargée de mission) - SG/DNUM/UNI/DRC <leslie.lemaire@developpement-durable.gouv.fr>
` Re: Cast to regrole on a literal string in a PL/pgSQL function
2025-09-30 15:29 UTC Tom Lane <tgl@sss.pgh.pa.us>
[5+ messages in thread]
BUG #19067: On master at commit 66cdef4425f3, "psql -c 'select 1' dbname" causes the backend to seg fault
2025-09-26 19:50 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #19067: On master at commit 66cdef4425f3, "psql -c 'select 1' dbname" causes the backend to seg fault
2025-09-27 09:07 UTC David Rowley <dgrowleyml@gmail.com>
` Re: BUG #19067: On master at commit 66cdef4425f3, "psql -c 'select 1' dbname" causes the backend to seg fault
2025-09-29 15:28 UTC Todd Cook <cookt@blackduck.com>
` Re: BUG #19067: On master at commit 66cdef4425f3, "psql -c 'select 1' dbname" causes the backend to seg fault
2025-09-29 15:55 UTC Tom Lane <tgl@sss.pgh.pa.us>
[4+ messages in thread]
The issue of incorrect width estimation in UNION queries
2025-09-24 06:13 UTC =?gb18030?B?c3Vudy5mbnN0?= <936739278@qq.com>
` Re: The issue of incorrect width estimation in UNION queries
2025-09-24 10:47 UTC David Rowley <dgrowleyml@gmail.com>
` Re: The issue of incorrect width estimation in UNION queries
2025-09-25 21:42 UTC David Rowley <dgrowleyml@gmail.com>
` Re: The issue of incorrect width estimation in UNION queries
2025-09-29 01:50 UTC David Rowley <dgrowleyml@gmail.com>
[4+ messages in thread]
BUG #19066: postgresql-18.0/src/backend/optimizer/geqo/geqo_ox2.c:86: Array index check in wrong place ?
2025-09-26 09:51 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #19066: postgresql-18.0/src/backend/optimizer/geqo/geqo_ox2.c:86: Array index check in wrong place ?
2025-09-26 14:53 UTC Tom Lane <tgl@sss.pgh.pa.us>
[2+ messages in thread]
BUG #19064: Trigger allows creation with invalid column references but fails at runtime
2025-09-26 07:36 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #19064: Trigger allows creation with invalid column references but fails at runtime
2025-09-26 12:46 UTC David G. Johnston <david.g.johnston@gmail.com>
` Re: BUG #19064: Trigger allows creation with invalid column references but fails at runtime
2025-09-26 12:59 UTC Rahila Syed <rahilasyed90@gmail.com>
` Re: BUG #19064: Trigger allows creation with invalid column references but fails at runtime
2025-09-26 13:35 UTC Anthony Sotolongo <asotolongo@gmail.com>
[4+ messages in thread]
BUG #19065: postgresql-18.0/src/bin/pg_combinebackup/reconstruct.c:230: Array sanity check in wrong place ?
2025-09-26 09:48 UTC PG Bug reporting form <noreply@postgresql.org>
Issue with PostgreSQL 18.0 Docker image volume mount (/var/lib/postgresql/data symlink)
2025-09-26 05:53 UTC Pavel Hushcha <paul.fastest@gmail.com>
` Re: Issue with PostgreSQL 18.0 Docker image volume mount (/var/lib/postgresql/data symlink)
2025-09-26 09:14 UTC Magnus Hagander <magnus@hagander.net>
[2+ messages in thread]
BUG #19058: Empty repomd.xml.asc file
2025-09-19 11:49 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #19058: Empty repomd.xml.asc file
2025-09-25 10:54 UTC Devrim Gündüz <devrim@gunduz.org>
[2+ messages in thread]
BUG #19063: Heavily nesting trivial ROW projections produces out of memory error
2025-09-24 14:06 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #19063: Heavily nesting trivial ROW projections produces out of memory error
2025-09-24 18:43 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #19063: Heavily nesting trivial ROW projections produces out of memory error
2025-09-25 08:30 UTC Lukas Eder <lukas.eder@gmail.com>
[3+ messages in thread]
=?gb18030?B?u9i4tKO6IFRoZSBpc3N1ZSBvZiBpbmNvcnJlY3Qg?= =?gb18030?B?d2lkdGggZXN0aW1hdGlvbiBpbiBVTklPTiBxdWVy?= =?gb18030?B?aWVz?=
2025-09-24 11:27 UTC =?gb18030?B?V2VpIFN1bg==?= <936739278@qq.com>
Lock timeouts and unusual spikes in replication lag with logical parallel transaction streaming
2025-08-11 06:20 UTC Zane Duffield <duffieldzane@gmail.com>
` Re: Lock timeouts and unusual spikes in replication lag with logical parallel transaction streaming
2025-08-11 10:55 UTC Amit Kapila <amit.kapila16@gmail.com>
` RE: Lock timeouts and unusual spikes in replication lag with logical parallel transaction streaming
2025-08-11 11:27 UTC Zhijie Hou (Fujitsu) <houzj.fnst@fujitsu.com>
` RE: Lock timeouts and unusual spikes in replication lag with logical parallel transaction streaming
2025-08-18 11:48 UTC Zhijie Hou (Fujitsu) <houzj.fnst@fujitsu.com>
` RE: Lock timeouts and unusual spikes in replication lag with logical parallel transaction streaming
2025-08-18 11:51 UTC Zhijie Hou (Fujitsu) <houzj.fnst@fujitsu.com>
` Re: Lock timeouts and unusual spikes in replication lag with logical parallel transaction streaming
2025-08-20 05:38 UTC Zane Duffield <duffieldzane@gmail.com>
` RE: Lock timeouts and unusual spikes in replication lag with logical parallel transaction streaming
2025-08-20 09:58 UTC Hayato Kuroda (Fujitsu) <kuroda.hayato@fujitsu.com>
` Re: Lock timeouts and unusual spikes in replication lag with logical parallel transaction streaming
2025-08-21 04:26 UTC Amit Kapila <amit.kapila16@gmail.com>
` Re: Lock timeouts and unusual spikes in replication lag with logical parallel transaction streaming
2025-09-18 04:17 UTC Zane Duffield <duffieldzane@gmail.com>
` Re: Lock timeouts and unusual spikes in replication lag with logical parallel transaction streaming
2025-09-22 08:36 UTC Amit Kapila <amit.kapila16@gmail.com>
` Re: Lock timeouts and unusual spikes in replication lag with logical parallel transaction streaming
2025-09-24 08:34 UTC Amit Kapila <amit.kapila16@gmail.com>
[11+ messages in thread]
BUG #19061: I downloaded version 17 of postgreSQL and it was lagging very much
2025-09-23 16:17 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #19061: I downloaded version 17 of postgreSQL and it was lagging very much
2025-09-24 05:21 UTC David Rowley <dgrowleyml@gmail.com>
[2+ messages in thread]
Numeric Type Precision Not Respected in Function or Procedure Arguments
2025-09-22 19:39 UTC Aaron Ackerman <aackerman@goodmorning.com>
` Re: Numeric Type Precision Not Respected in Function or Procedure Arguments
2025-09-22 21:31 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: Numeric Type Precision Not Respected in Function or Procedure Arguments
2025-09-22 21:33 UTC David G. Johnston <david.g.johnston@gmail.com>
[3+ messages in thread]
Maybe problems with autovaccum?
2025-09-22 12:06 UTC Franz Philipp Moser <fpmedv@gmail.com>
regexp_replace not respecting greediness
2025-09-19 12:36 UTC Simon Ellmann <simon.ellmann@tum.de>
` Re: regexp_replace not respecting greediness
2025-09-19 14:09 UTC David G. Johnston <david.g.johnston@gmail.com>
` Re: regexp_replace not respecting greediness
2025-09-19 16:01 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: regexp_replace not respecting greediness
2025-09-22 08:07 UTC Simon Ellmann <simon.ellmann@tum.de>
[4+ messages in thread]
coredump of language internal function
2025-09-22 04:56 UTC myzhen <zhenmingyang@yeah.net>
` Re: coredump of language internal function
2025-09-22 05:05 UTC Tom Lane <tgl@sss.pgh.pa.us>
[2+ messages in thread]
BUG #19059: PostgreSQL fails to evaluate the cheaper expression first, leading to 45X performance degradation
2025-09-20 16:08 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #19059: PostgreSQL fails to evaluate the cheaper expression first, leading to 45X performance degradation
2025-09-20 21:19 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #19059: PostgreSQL fails to evaluate the cheaper expression first, leading to 45X performance degradation
2025-09-20 22:54 UTC Christophe Pettus <xof@thebuild.com>
` Re: BUG #19059: PostgreSQL fails to evaluate the cheaper expression first, leading to 45X performance degradation
2025-09-20 23:19 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #19059: PostgreSQL fails to evaluate the cheaper expression first, leading to 45X performance degradation
2025-09-21 09:09 UTC Vik Fearing <vik@postgresfriends.org>
` Re: BUG #19059: PostgreSQL fails to evaluate the cheaper expression first, leading to 45X performance degradation
2025-09-21 16:05 UTC =?utf-8?B?SmluaHVpIExhaQ==?= <jinhui.lai@qq.com>
[6+ messages in thread]
BUG #19056: ExecInitPartitionExecPruning segfault due to NULL es_part_prune_infos
2025-09-17 15:08 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #19056: ExecInitPartitionExecPruning segfault due to NULL es_part_prune_infos
2025-09-17 21:43 UTC David Rowley <dgrowleyml@gmail.com>
` Re: BUG #19056: ExecInitPartitionExecPruning segfault due to NULL es_part_prune_infos
2025-09-17 22:32 UTC David Rowley <dgrowleyml@gmail.com>
` Re: BUG #19056: ExecInitPartitionExecPruning segfault due to NULL es_part_prune_infos
2025-09-18 01:33 UTC Amit Langote <amitlangote09@gmail.com>
` Re: BUG #19056: ExecInitPartitionExecPruning segfault due to NULL es_part_prune_infos
2025-09-18 01:58 UTC feichanghong <feichanghong@qq.com>
` Re: BUG #19056: ExecInitPartitionExecPruning segfault due to NULL es_part_prune_infos
2025-09-18 03:10 UTC Amit Langote <amitlangote09@gmail.com>
` Re: BUG #19056: ExecInitPartitionExecPruning segfault due to NULL es_part_prune_infos
2025-09-18 03:37 UTC Amit Langote <amitlangote09@gmail.com>
` Re: BUG #19056: ExecInitPartitionExecPruning segfault due to NULL es_part_prune_infos
2025-09-18 03:47 UTC David Rowley <dgrowleyml@gmail.com>
` Re: BUG #19056: ExecInitPartitionExecPruning segfault due to NULL es_part_prune_infos
2025-09-18 04:11 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #19056: ExecInitPartitionExecPruning segfault due to NULL es_part_prune_infos
2025-09-18 04:19 UTC David Rowley <dgrowleyml@gmail.com>
` Re: BUG #19056: ExecInitPartitionExecPruning segfault due to NULL es_part_prune_infos
2025-09-18 04:29 UTC David Rowley <dgrowleyml@gmail.com>
` Re: BUG #19056: ExecInitPartitionExecPruning segfault due to NULL es_part_prune_infos
2025-09-18 04:38 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #19056: ExecInitPartitionExecPruning segfault due to NULL es_part_prune_infos
2025-09-18 04:56 UTC Amit Langote <amitlangote09@gmail.com>
` Re: BUG #19056: ExecInitPartitionExecPruning segfault due to NULL es_part_prune_infos
2025-09-18 05:15 UTC David Rowley <dgrowleyml@gmail.com>
` Re: BUG #19056: ExecInitPartitionExecPruning segfault due to NULL es_part_prune_infos
2025-09-18 06:09 UTC Amit Langote <amitlangote09@gmail.com>
` Re: BUG #19056: ExecInitPartitionExecPruning segfault due to NULL es_part_prune_infos
2025-09-18 06:15 UTC feichanghong <feichanghong@qq.com>
` Re: BUG #19056: ExecInitPartitionExecPruning segfault due to NULL es_part_prune_infos
2025-09-18 06:20 UTC Amit Langote <amitlangote09@gmail.com>
` Re: BUG #19056: ExecInitPartitionExecPruning segfault due to NULL es_part_prune_infos
2025-09-18 07:05 UTC David Rowley <dgrowleyml@gmail.com>
` Re: BUG #19056: ExecInitPartitionExecPruning segfault due to NULL es_part_prune_infos
2025-09-18 08:25 UTC Amit Langote <amitlangote09@gmail.com>
` Re: BUG #19056: ExecInitPartitionExecPruning segfault due to NULL es_part_prune_infos
2025-09-19 02:05 UTC David Rowley <dgrowleyml@gmail.com>
` Re: BUG #19056: ExecInitPartitionExecPruning segfault due to NULL es_part_prune_infos
2025-09-19 02:42 UTC Amit Langote <amitlangote09@gmail.com>
[21+ messages in thread]
BUG #19057: Installing postgresql-15 from the repostory installs a mix of postgresql 15 and 17
2025-09-18 21:24 UTC PG Bug reporting form <noreply@postgresql.org>
"unexpected duplicate for tablespace" problem in logical replication
2022-04-06 02:14 UTC wangsh.fnst@fujitsu.com <wangsh.fnst@fujitsu.com>
` RE: "unexpected duplicate for tablespace" problem in logical replication
2022-04-08 09:44 UTC osumi.takamichi@fujitsu.com <osumi.takamichi@fujitsu.com>
` RE: "unexpected duplicate for tablespace" problem in logical replication
2022-04-11 07:40 UTC osumi.takamichi@fujitsu.com <osumi.takamichi@fujitsu.com>
` Re: "unexpected duplicate for tablespace" problem in logical replication
2022-04-11 10:24 UTC wangsh.fnst@fujitsu.com <wangsh.fnst@fujitsu.com>
` Re: "unexpected duplicate for tablespace" problem in logical replication
2022-04-12 02:45 UTC Kyotaro Horiguchi <horikyota.ntt@gmail.com>
` Re: "unexpected duplicate for tablespace" problem in logical replication
2022-04-12 03:36 UTC wangsh.fnst@fujitsu.com <wangsh.fnst@fujitsu.com>
` Re: "unexpected duplicate for tablespace" problem in logical replication
2022-04-19 06:23 UTC Masahiko Sawada <sawada.mshk@gmail.com>
` Re: "unexpected duplicate for tablespace" problem in logical replication
2024-01-08 05:02 UTC vignesh C <vignesh21@gmail.com>
` Re: "unexpected duplicate for tablespace" problem in logical replication
2024-01-12 08:37 UTC Kyotaro Horiguchi <horikyota.ntt@gmail.com>
` Re: "unexpected duplicate for tablespace" problem in logical replication
2024-01-15 21:32 UTC Robert Haas <robertmhaas@gmail.com>
` Re: "unexpected duplicate for tablespace" problem in logical replication
2024-01-16 01:58 UTC Kyotaro Horiguchi <horikyota.ntt@gmail.com>
` Re: "unexpected duplicate for tablespace" problem in logical replication
2024-02-02 15:49 UTC Robert Haas <robertmhaas@gmail.com>
` Re: "unexpected duplicate for tablespace" problem in logical replication
2024-03-18 06:35 UTC Michael Paquier <michael@paquier.xyz>
` Re: "unexpected duplicate for tablespace" problem in logical replication
2024-07-24 21:51 UTC Masahiko Sawada <sawada.mshk@gmail.com>
` Re: "unexpected duplicate for tablespace" problem in logical replication
2025-03-25 10:01 UTC vignesh C <vignesh21@gmail.com>
` Re: "unexpected duplicate for tablespace" problem in logical replication
2025-06-19 08:47 UTC Ashutosh Bapat <ashutosh.bapat.oss@gmail.com>
` Re: "unexpected duplicate for tablespace" problem in logical replication
2025-08-13 09:48 UTC Ashutosh Bapat <ashutosh.bapat.oss@gmail.com>
` Re: "unexpected duplicate for tablespace" problem in logical replication
2025-08-13 09:59 UTC Ashutosh Bapat <ashutosh.bapat.oss@gmail.com>
` Re: "unexpected duplicate for tablespace" problem in logical replication
2025-08-21 06:12 UTC Michael Paquier <michael@paquier.xyz>
` Re: "unexpected duplicate for tablespace" problem in logical replication
2025-08-21 14:24 UTC Ashutosh Bapat <ashutosh.bapat.oss@gmail.com>
` Re: "unexpected duplicate for tablespace" problem in logical replication
2025-08-21 21:36 UTC Michael Paquier <michael@paquier.xyz>
` Re: "unexpected duplicate for tablespace" problem in logical replication
2025-09-18 12:07 UTC Ashutosh Bapat <ashutosh.bapat.oss@gmail.com>
` Re: "unexpected duplicate for tablespace" problem in logical replication
2025-09-18 12:17 UTC Andres Freund <andres@anarazel.de>
` Re: "unexpected duplicate for tablespace" problem in logical replication
2025-09-18 12:22 UTC Andres Freund <andres@anarazel.de>
` Re: "unexpected duplicate for tablespace" problem in logical replication
2025-09-18 15:30 UTC Ashutosh Bapat <ashutosh.bapat.oss@gmail.com>
[25+ 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