pg.ddx.io pgsql-bugs@postgresql.org mailing list archive
help / color / mirror / Atom feedPostgreSQL v15.12 fails to perform PG_UPGRADE from v13 and v9 on Windows
2025-03-20 15:14 UTC Ben Caspi <benc@aidoc.com>
` Re: PostgreSQL v15.12 fails to perform PG_UPGRADE from v13 and v9 on Windows
2025-04-04 12:30 UTC Manika Singhal <manika.singhal@enterprisedb.com>
` Re: PostgreSQL v15.12 fails to perform PG_UPGRADE from v13 and v9 on Windows
2025-04-07 14:59 UTC Avi Uziel <avi.uziel@aidoc.com>
` Re: PostgreSQL v15.12 fails to perform PG_UPGRADE from v13 and v9 on Windows
2025-04-08 05:50 UTC Laurenz Albe <laurenz.albe@cybertec.at>
` Re: PostgreSQL v15.12 fails to perform PG_UPGRADE from v13 and v9 on Windows
2025-04-09 23:49 UTC Thomas Munro <thomas.munro@gmail.com>
` Re: PostgreSQL v15.12 fails to perform PG_UPGRADE from v13 and v9 on Windows
2025-04-10 07:02 UTC Manika Singhal <manika.singhal@enterprisedb.com>
` Re: PostgreSQL v15.12 fails to perform PG_UPGRADE from v13 and v9 on Windows
2025-04-10 07:14 UTC Thomas Munro <thomas.munro@gmail.com>
` Re: PostgreSQL v15.12 fails to perform PG_UPGRADE from v13 and v9 on Windows
2025-04-15 14:51 UTC Manika Singhal <manika.singhal@enterprisedb.com>
` Re: PostgreSQL v15.12 fails to perform PG_UPGRADE from v13 and v9 on Windows
2025-04-15 16:10 UTC Nico Williams <nico@cryptonector.com>
` Re: PostgreSQL v15.12 fails to perform PG_UPGRADE from v13 and v9 on Windows
2025-04-15 21:11 UTC Thomas Munro <thomas.munro@gmail.com>
` Re: PostgreSQL v15.12 fails to perform PG_UPGRADE from v13 and v9 on Windows
2025-04-15 21:33 UTC Nico Williams <nico@cryptonector.com>
` Re: PostgreSQL v15.12 fails to perform PG_UPGRADE from v13 and v9 on Windows
2025-04-16 00:34 UTC Thomas Munro <thomas.munro@gmail.com>
` Re: PostgreSQL v15.12 fails to perform PG_UPGRADE from v13 and v9 on Windows
2025-04-17 19:18 UTC Nico Williams <nico@cryptonector.com>
` Re: PostgreSQL v15.12 fails to perform PG_UPGRADE from v13 and v9 on Windows
2025-04-17 19:31 UTC Nico Williams <nico@cryptonector.com>
` Re: PostgreSQL v15.12 fails to perform PG_UPGRADE from v13 and v9 on Windows
2025-04-22 10:58 UTC Avi Uziel <avi.uziel@aidoc.com>
` Re: PostgreSQL v15.12 fails to perform PG_UPGRADE from v13 and v9 on Windows
2025-04-22 11:30 UTC Manika Singhal <manika.singhal@enterprisedb.com>
` Re: PostgreSQL v15.12 fails to perform PG_UPGRADE from v13 and v9 on Windows
2025-04-22 11:39 UTC Avi Uziel <avi.uziel@aidoc.com>
` Re: PostgreSQL v15.12 fails to perform PG_UPGRADE from v13 and v9 on Windows
2025-04-23 05:40 UTC Manika Singhal <manika.singhal@enterprisedb.com>
[18+ messages in thread]
BUG #18901: Bug in Perl-Script "src/backend/nodes/gen_node_support.pl"
2025-04-22 16:39 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18901: Bug in Perl-Script "src/backend/nodes/gen_node_support.pl"
2025-04-22 17:25 UTC Tom Lane <tgl@sss.pgh.pa.us>
[2+ messages in thread]
BUG #18872: The current OS X version is not supported
2025-03-30 19:33 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18872: The current OS X version is not supported
2025-03-30 21:07 UTC Daniel Gustafsson <daniel@yesql.se>
` Re: BUG #18872: The current OS X version is not supported
2025-04-22 13:40 UTC Dave Cramer <davecramer@postgres.rocks>
[3+ messages in thread]
BUG #18900: Missing RPM python3-kazoo for RHEL9 - patroni RPM cannot be installed
2025-04-22 09:38 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18900: Missing RPM python3-kazoo for RHEL9 - patroni RPM cannot be installed
2025-04-22 12:27 UTC Robert Treat <rob@xzilla.net>
[2+ messages in thread]
ERROR: tuple to be updated was already modified by an operation triggered by the current command
2025-01-23 09:11 UTC Richard Guo <guofenglinux@gmail.com>
` Re: ERROR: tuple to be updated was already modified by an operation triggered by the current command
2025-04-11 12:48 UTC Robins Tharakan <tharakan@gmail.com>
` Re: ERROR: tuple to be updated was already modified by an operation triggered by the current command
2025-04-11 14:41 UTC Noah Misch <noah@leadboat.com>
` Re: ERROR: tuple to be updated was already modified by an operation triggered by the current command
2025-04-21 04:06 UTC Noah Misch <noah@leadboat.com>
[4+ messages in thread]
Error when using array_agg with filter where clause in pg16 and pg17
2025-04-08 12:38 UTC Kaimeh <kkaimeh@gmail.com>
` Re: Error when using array_agg with filter where clause in pg16 and pg17
2025-04-08 15:32 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: Error when using array_agg with filter where clause in pg16 and pg17
2025-04-08 23:55 UTC David Rowley <dgrowleyml@gmail.com>
` Re: Error when using array_agg with filter where clause in pg16 and pg17
2025-04-09 00:25 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: Error when using array_agg with filter where clause in pg16 and pg17
2025-04-09 00:43 UTC David Rowley <dgrowleyml@gmail.com>
` Re: Error when using array_agg with filter where clause in pg16 and pg17
2025-04-09 00:52 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: Error when using array_agg with filter where clause in pg16 and pg17
2025-04-09 00:54 UTC David Rowley <dgrowleyml@gmail.com>
` Re: Error when using array_agg with filter where clause in pg16 and pg17
2025-04-09 01:50 UTC David Rowley <dgrowleyml@gmail.com>
` Re: Error when using array_agg with filter where clause in pg16 and pg17
2025-04-09 02:36 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: Error when using array_agg with filter where clause in pg16 and pg17
2025-04-09 02:55 UTC David Rowley <dgrowleyml@gmail.com>
` Re: Error when using array_agg with filter where clause in pg16 and pg17
2025-04-20 10:21 UTC David Rowley <dgrowleyml@gmail.com>
[11+ messages in thread]
BUG #18896: A potential problem in heap_page_items (pageinspect, PG-17)
2025-04-16 20:21 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18896: A potential problem in heap_page_items (pageinspect, PG-17)
2025-04-19 19:33 UTC Tom Lane <tgl@sss.pgh.pa.us>
[2+ messages in thread]
BUG #18899: FreeBSD, assembly by means of GCC with ASAN ends with error: undef reference to backtrace_symbols_fd
2025-04-18 12:38 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18899: FreeBSD, assembly by means of GCC with ASAN ends with error: undef reference to backtrace_symbols_fd
2025-04-18 17:38 UTC Tom Lane <tgl@sss.pgh.pa.us>
[2+ messages in thread]
BUG #18898: replication process not working... sometimes
2025-04-17 00:09 UTC PG Bug reporting form <noreply@postgresql.org>
` RE: BUG #18898: replication process not working... sometimes
2025-04-18 12:31 UTC Hayato Kuroda (Fujitsu) <kuroda.hayato@fujitsu.com>
[2+ messages in thread]
BUG #18892: When the view already exists, CREATE OR REPLACE VIEW does not check whether the table exists.
2025-04-12 02:34 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18892: When the view already exists, CREATE OR REPLACE VIEW does not check whether the table exists.
2025-04-12 19:19 UTC Kirill Reshke <reshkekirill@gmail.com>
` Re: BUG #18892: When the view already exists, CREATE OR REPLACE VIEW does not check whether the table exists.
2025-04-12 19:32 UTC David G. Johnston <david.g.johnston@gmail.com>
` Re: BUG #18892: When the view already exists, CREATE OR REPLACE VIEW does not check whether the table exists.
2025-04-13 13:09 UTC Kirill Reshke <reshkekirill@gmail.com>
` Re: BUG #18892: When the view already exists, CREATE OR REPLACE VIEW does not check whether the table exists.
2025-04-13 14:05 UTC Tom Lane <tgl@sss.pgh.pa.us>
` 回复: BUG #18892: When the view already exists, CREATE OR REPLACE VIEW does not check whether the table exists.
2025-04-14 08:55 UTC Gang Chen <gchen@s2now.com>
` Re: 回复: BUG #18892: When the view already exists, CREATE OR REPLACE VIEW does not check whether the table exists.
2025-04-16 16:43 UTC Bruce Momjian <bruce@momjian.us>
[7+ messages in thread]
BUG #18895: Installation failure on Fedora 42 due to missing repos
2025-04-16 08:59 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18895: Installation failure on Fedora 42 due to missing repos
2025-04-16 12:20 UTC Laurenz Albe <laurenz.albe@cybertec.at>
` Re: BUG #18895: Installation failure on Fedora 42 due to missing repos
2025-04-16 12:41 UTC Devrim Gündüz <devrim@gunduz.org>
` Re: BUG #18895: Installation failure on Fedora 42 due to missing repos
2025-04-16 13:26 UTC Devrim Gündüz <devrim@gunduz.org>
[4+ messages in thread]
BUG #18894: values of JLC_COLLATE and LC_CTYPE in the database have changed from Japanese_Japan.932 to ja-jp
2025-04-14 06:08 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18894: values of JLC_COLLATE and LC_CTYPE in the database have changed from Japanese_Japan.932 to ja-jp
2025-04-14 17:30 UTC Laurenz Albe <laurenz.albe@cybertec.at>
` Re: BUG #18894: values of JLC_COLLATE and LC_CTYPE in the database have changed from Japanese_Japan.932 to ja-jp
2025-04-15 14:46 UTC Manika Singhal <manika.singhal@enterprisedb.com>
[3+ messages in thread]
Missing whitespace in pg_restore manpage
2025-04-14 09:55 UTC Lele Gaifax <lele@metapensiero.it>
` Re: Missing whitespace in pg_restore manpage
2025-04-15 05:47 UTC Fujii Masao <masao.fujii@oss.nttdata.com>
` Re: Missing whitespace in pg_restore manpage
2025-04-15 05:56 UTC Lele Gaifax <lele@metapensiero.it>
` Re: Missing whitespace in pg_restore manpage
2025-04-15 14:19 UTC Fujii Masao <masao.fujii@oss.nttdata.com>
[4+ messages in thread]
BUG #18831: Particular queries using gin-indexes are not interruptible, resulting is resource usage concerns.
2025-03-05 17:49 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18831: Particular queries using gin-indexes are not interruptible, resulting is resource usage concerns.
2025-03-05 20:50 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #18831: Particular queries using gin-indexes are not interruptible, resulting is resource usage concerns.
2025-04-11 23:38 UTC Vinod Sridharan <vsridh90@gmail.com>
` Re: BUG #18831: Particular queries using gin-indexes are not interruptible, resulting is resource usage concerns.
2025-04-11 23:54 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #18831: Particular queries using gin-indexes are not interruptible, resulting is resource usage concerns.
2025-04-12 02:17 UTC Vinod Sridharan <vsridh90@gmail.com>
` Re: BUG #18831: Particular queries using gin-indexes are not interruptible, resulting is resource usage concerns.
2025-04-12 03:00 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #18831: Particular queries using gin-indexes are not interruptible, resulting is resource usage concerns.
2025-04-12 03:30 UTC Vinod Sridharan <vsridh90@gmail.com>
` Re: BUG #18831: Particular queries using gin-indexes are not interruptible, resulting is resource usage concerns.
2025-04-12 05:33 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #18831: Particular queries using gin-indexes are not interruptible, resulting is resource usage concerns.
2025-04-12 05:58 UTC Vinod Sridharan <vsridh90@gmail.com>
` Re: BUG #18831: Particular queries using gin-indexes are not interruptible, resulting is resource usage concerns.
2025-04-12 16:40 UTC Tom Lane <tgl@sss.pgh.pa.us>
[10+ messages in thread]
BUG #18889: /src/backend/utils/adt/network.c condition is always false
2025-04-10 16:41 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18889: /src/backend/utils/adt/network.c condition is always false
2025-04-10 18:19 UTC Tom Lane <tgl@sss.pgh.pa.us>
[2+ messages in thread]
BUG #18888: /src/interfaces/ecpg/preproc/descriptor.c possible NULL dereference
2025-04-10 16:39 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18888: /src/interfaces/ecpg/preproc/descriptor.c possible NULL dereference
2025-04-10 18:17 UTC Euler Taveira <euler@eulerto.com>
[2+ messages in thread]
BUG #18891: /src/include/lib/simplehash.h possible palloc0 problems
2025-04-10 16:47 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18891: /src/include/lib/simplehash.h possible palloc0 problems
2025-04-10 18:04 UTC Tom Lane <tgl@sss.pgh.pa.us>
[2+ messages in thread]
BUG #18890: /src/timezone/localtime.c condition always false
2025-04-10 16:44 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18890: /src/timezone/localtime.c condition always false
2025-04-10 18:02 UTC Tom Lane <tgl@sss.pgh.pa.us>
[2+ messages in thread]
BUG #18887: Inner join returns non-existent data.
2025-04-10 15:50 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18887: Inner join returns non-existent data.
2025-04-10 17:51 UTC Tom Lane <tgl@sss.pgh.pa.us>
[2+ messages in thread]
Help Please!
2025-04-09 18:31 UTC Carrie Ray <rdnkprncss03@aol.com>
` Re: Help Please!
2025-04-10 11:30 UTC Daniel Gustafsson <daniel@yesql.se>
` Re: Help Please!
2025-04-10 12:34 UTC Kieran McCusker <kieran.mccusker@gmail.com>
[3+ messages in thread]
BUG #18886: identity duplicate key
2025-04-09 23:04 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18886: identity duplicate key
2025-04-10 11:13 UTC hubert depesz lubaczewski <depesz@depesz.com>
` Re: BUG #18886: identity duplicate key
2025-04-10 11:18 UTC hubert depesz lubaczewski <depesz@depesz.com>
[3+ messages in thread]
BUG #18815: Logical replication worker Segmentation fault
2025-02-17 10:52 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18815: Logical replication worker Segmentation fault
2025-02-17 16:39 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #18815: Logical replication worker Segmentation fault
2025-02-17 19:17 UTC Sergey Belyashov <sergey.belyashov@gmail.com>
` Re: BUG #18815: Logical replication worker Segmentation fault
2025-02-17 19:43 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #18815: Logical replication worker Segmentation fault
2025-02-17 20:13 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #18815: Logical replication worker Segmentation fault
2025-02-17 20:57 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #18815: Logical replication worker Segmentation fault
2025-02-17 23:37 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #18815: Logical replication worker Segmentation fault
2025-02-18 01:51 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #18815: Logical replication worker Segmentation fault
2025-02-18 06:56 UTC Sergey Belyashov <sergey.belyashov@gmail.com>
` Re: BUG #18815: Logical replication worker Segmentation fault
2025-02-18 16:54 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #18815: Logical replication worker Segmentation fault
2025-02-18 17:41 UTC Sergey Belyashov <sergey.belyashov@gmail.com>
` Re: BUG #18815: Logical replication worker Segmentation fault
2025-02-18 20:38 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #18815: Logical replication worker Segmentation fault
2025-02-18 22:24 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #18815: Logical replication worker Segmentation fault
2025-02-19 06:55 UTC Sergey Belyashov <sergey.belyashov@gmail.com>
` Re: BUG #18815: Logical replication worker Segmentation fault
2025-02-19 07:06 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #18815: Logical replication worker Segmentation fault
2025-02-19 21:55 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #18815: Logical replication worker Segmentation fault
2025-02-20 19:17 UTC Sergey Belyashov <sergey.belyashov@gmail.com>
` RE: BUG #18815: Logical replication worker Segmentation fault
2025-03-26 05:07 UTC Zhijie Hou (Fujitsu) <houzj.fnst@fujitsu.com>
` Re: BUG #18815: Logical replication worker Segmentation fault
2025-04-07 09:37 UTC Amit Kapila <amit.kapila16@gmail.com>
` RE: BUG #18815: Logical replication worker Segmentation fault
2025-04-07 09:58 UTC Zhijie Hou (Fujitsu) <houzj.fnst@fujitsu.com>
` Re: BUG #18815: Logical replication worker Segmentation fault
2025-04-08 05:59 UTC Amit Kapila <amit.kapila16@gmail.com>
` RE: BUG #18815: Logical replication worker Segmentation fault
2025-04-08 06:56 UTC Zhijie Hou (Fujitsu) <houzj.fnst@fujitsu.com>
` Re: BUG #18815: Logical replication worker Segmentation fault
2025-04-09 09:29 UTC Amit Kapila <amit.kapila16@gmail.com>
[23+ messages in thread]
BUG #18884: The CURRENT_TIMESTAMP value being returned in UTC-2.
2025-04-08 13:56 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18884: The CURRENT_TIMESTAMP value being returned in UTC-2.
2025-04-08 13:58 UTC Test Test <testtest12423@gmail.com>
` Re: BUG #18884: The CURRENT_TIMESTAMP value being returned in UTC-2.
2025-04-08 14:32 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #18884: The CURRENT_TIMESTAMP value being returned in UTC-2.
2025-04-08 14:44 UTC David G. Johnston <david.g.johnston@gmail.com>
[4+ messages in thread]
BUG #18883: Epoch issue
2025-04-08 12:00 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18883: Epoch issue
2025-04-08 12:29 UTC David G. Johnston <david.g.johnston@gmail.com>
[2+ messages in thread]
BUG #18882: Unexpected write skew at SERIALIZABLE with psycopg2.connect()
2025-04-08 07:10 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18882: Unexpected write skew at SERIALIZABLE with psycopg2.connect()
2025-04-08 11:09 UTC Thomas Munro <thomas.munro@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