pg.ddx.io pgsql-bugs@postgresql.org mailing list archive
help / color / mirror / Atom feedBUG #18979: pg_upgrade to PG17 fails if max_slot_wal_keep_size is not set to -1
2025-07-06 13:58 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18979: pg_upgrade to PG17 fails if max_slot_wal_keep_size is not set to -1
2025-07-06 15:11 UTC David G. Johnston <david.g.johnston@gmail.com>
` Re: BUG #18979: pg_upgrade to PG17 fails if max_slot_wal_keep_size is not set to -1
2025-07-06 15:26 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #18979: pg_upgrade to PG17 fails if max_slot_wal_keep_size is not set to -1
2025-07-06 16:41 UTC David G. Johnston <david.g.johnston@gmail.com>
` Re: BUG #18979: pg_upgrade to PG17 fails if max_slot_wal_keep_size is not set to -1
2025-07-06 16:47 UTC David G. Johnston <david.g.johnston@gmail.com>
` Re: BUG #18979: pg_upgrade to PG17 fails if max_slot_wal_keep_size is not set to -1
2025-07-06 17:53 UTC Tom Lane <tgl@sss.pgh.pa.us>
[6+ messages in thread]
functional index search path issue.
2025-07-05 11:45 UTC Kirill Reshke <reshkekirill@gmail.com>
` Re: functional index search path issue.
2025-07-05 14:53 UTC David G. Johnston <david.g.johnston@gmail.com>
[2+ messages in thread]
BUG #18970: Atempt to alter type of table column used in row type with check leads to assertion failure
2025-06-28 07:00 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18970: Atempt to alter type of table column used in row type with check leads to assertion failure
2025-06-29 05:28 UTC jian he <jian.universality@gmail.com>
` Re: BUG #18970: Atempt to alter type of table column used in row type with check leads to assertion failure
2025-06-29 17:01 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #18970: Atempt to alter type of table column used in row type with check leads to assertion failure
2025-06-29 17:32 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #18970: Atempt to alter type of table column used in row type with check leads to assertion failure
2025-06-30 01:47 UTC jian he <jian.universality@gmail.com>
` Re: BUG #18970: Atempt to alter type of table column used in row type with check leads to assertion failure
2025-06-30 02:23 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #18970: Atempt to alter type of table column used in row type with check leads to assertion failure
2025-06-30 06:04 UTC jian he <jian.universality@gmail.com>
` Re: BUG #18970: Atempt to alter type of table column used in row type with check leads to assertion failure
2025-06-30 15:14 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #18970: Atempt to alter type of table column used in row type with check leads to assertion failure
2025-07-01 03:25 UTC jian he <jian.universality@gmail.com>
` Re: BUG #18970: Atempt to alter type of table column used in row type with check leads to assertion failure
2025-07-01 19:52 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #18970: Atempt to alter type of table column used in row type with check leads to assertion failure
2025-07-03 17:48 UTC Tom Lane <tgl@sss.pgh.pa.us>
[11+ messages in thread]
BUG #18978: Index does not work in aggregate function filter
2025-07-03 16:13 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18978: Index does not work in aggregate function filter
2025-07-03 16:36 UTC David G. Johnston <david.g.johnston@gmail.com>
[2+ messages in thread]
BUG #18977: Unexpected result of function to_char
2025-07-03 13:23 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18977: Unexpected result of function to_char
2025-07-03 14:40 UTC Laurenz Albe <laurenz.albe@cybertec.at>
` Re: BUG #18977: Unexpected result of function to_char
2025-07-03 15:06 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #18977: Unexpected result of function to_char
2025-07-03 15:49 UTC =?utf-8?B?WmhhbmdDaGk=?= <798604270@qq.com>
[4+ messages in thread]
BUG #16931: source code problem about commit_ts
2021-03-18 04:36 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #16931: source code problem about commit_ts
2021-03-18 10:19 UTC Fujii Masao <masao.fujii@oss.nttdata.com>
` Re: BUG #16931: source code problem about commit_ts
2021-03-24 09:05 UTC Alvaro Herrera <alvherre@alvh.no-ip.org>
` Re: BUG #16931: source code problem about commit_ts
2021-03-24 10:25 UTC Fujii Masao <masao.fujii@oss.nttdata.com>
` Re: BUG #16931: source code problem about commit_ts
2021-03-24 16:39 UTC Alvaro Herrera <alvherre@alvh.no-ip.org>
` Re: BUG #16931: source code problem about commit_ts
2021-03-25 02:59 UTC Fujii Masao <masao.fujii@oss.nttdata.com>
` Re: BUG #16931: source code problem about commit_ts
2021-04-09 22:42 UTC Alvaro Herrera <alvherre@alvh.no-ip.org>
` Re: BUG #16931: source code problem about commit_ts
2021-04-11 15:09 UTC Fujii Masao <masao.fujii@oss.nttdata.com>
` Re: BUG #16931: source code problem about commit_ts
2025-07-02 01:42 UTC Andy Fan <zhihuifan1213@163.com>
` Re: BUG #16931: source code problem about commit_ts
2025-07-02 08:44 UTC Fujii Masao <masao.fujii@oss.nttdata.com>
` Re: BUG #16931: source code problem about commit_ts
2025-07-03 13:33 UTC Andy Fan <zhihuifan1213@163.com>
` Re: BUG #16931: source code problem about commit_ts
2025-07-03 14:42 UTC Fujii Masao <masao.fujii@oss.nttdata.com>
[12+ messages in thread]
BUG #18976: -0.0 with float8 will be transformed to 0 in prepare statement but not in normal execution
2025-07-03 03:03 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18976: -0.0 with float8 will be transformed to 0 in prepare statement but not in normal execution
2025-07-03 12:23 UTC Laurenz Albe <laurenz.albe@cybertec.at>
` Re: BUG #18976: -0.0 with float8 will be transformed to 0 inprepare statement but not in normal execution
2025-07-03 12:30 UTC =?utf-8?B?WmhhbmdDaGk=?= <798604270@qq.com>
` Re: BUG #18976: -0.0 with float8 will be transformed to 0 inprepare statement but not in normal execution
2025-07-03 13:27 UTC Laurenz Albe <laurenz.albe@cybertec.at>
` Re: BUG #18976: -0.0 with float8 will be transformed to 0 inpreparestatement but not in normal execution
2025-07-03 13:45 UTC =?utf-8?B?WmhhbmdDaGk=?= <798604270@qq.com>
[5+ messages in thread]
BUG #18974: Postgresql repeatable crash after pg_upgrade from 15 to 17.5 version in postgresql_fdw queries
2025-07-01 22:08 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18974: Postgresql repeatable crash after pg_upgrade from 15 to 17.5 version in postgresql_fdw queries
2025-07-02 00:03 UTC Maxim Boguk <maxim.boguk@gmail.com>
` Re: BUG #18974: Postgresql repeatable crash after pg_upgrade from 15 to 17.5 version in postgresql_fdw queries
2025-07-02 06:35 UTC Maxim Boguk <maxim.boguk@gmail.com>
` Re: BUG #18974: Postgresql repeatable crash after pg_upgrade from 15 to 17.5 version in postgresql_fdw queries
2025-07-02 07:04 UTC Maxim Boguk <maxim.boguk@gmail.com>
` Re: BUG #18974: Postgresql repeatable crash after pg_upgrade from 15 to 17.5 version in postgresql_fdw queries
2025-07-02 07:44 UTC Sergei Kornilov <sk@zsrv.org>
` Re: BUG #18974: Postgresql repeatable crash after pg_upgrade from 15 to 17.5 version in postgresql_fdw queries
2025-07-02 19:21 UTC Tom Lane <tgl@sss.pgh.pa.us>
[6+ messages in thread]
BUG #18975: PostgreSQL server doesn't process SQL request correctly over Windows replica of Linux server
2025-07-01 23:10 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18975: PostgreSQL server doesn't process SQL request correctly over Windows replica of Linux server
2025-07-02 13:49 UTC Laurenz Albe <laurenz.albe@cybertec.at>
[2+ messages in thread]
Logical replication 'invalid memory alloc request size 1585837200' after upgrading to 17.5
2025-05-19 11:46 UTC Duncan Sands <duncan.sands@deepbluecap.com>
` Re: Logical replication 'invalid memory alloc request size 1585837200' after upgrading to 17.5
2025-05-21 05:46 UTC Shlok Kyal <shlok.kyal.oss@gmail.com>
` Re: Logical replication 'invalid memory alloc request size 1585837200' after upgrading to 17.5
2025-05-21 05:48 UTC Amit Kapila <amit.kapila16@gmail.com>
` Re: Logical replication 'invalid memory alloc request size 1585837200' after upgrading to 17.5
2025-05-21 11:12 UTC Amit Kapila <amit.kapila16@gmail.com>
` Re: Logical replication 'invalid memory alloc request size 1585837200' after upgrading to 17.5
2025-05-21 11:30 UTC Duncan Sands <duncan.sands@deepbluecap.com>
` RE: Logical replication 'invalid memory alloc request size 1585837200' after upgrading to 17.5
2025-05-21 11:48 UTC Hayato Kuroda (Fujitsu) <kuroda.hayato@fujitsu.com>
` Re: Logical replication 'invalid memory alloc request size 1585837200' after upgrading to 17.5
2025-05-21 13:27 UTC Duncan Sands <duncan.sands@deepbluecap.com>
` Re: Logical replication 'invalid memory alloc request size 1585837200' after upgrading to 17.5
2025-05-21 18:24 UTC Masahiko Sawada <sawada.mshk@gmail.com>
` Re: Logical replication 'invalid memory alloc request size 1585837200' after upgrading to 17.5
2025-05-22 10:56 UTC Amit Kapila <amit.kapila16@gmail.com>
` Re: Logical replication 'invalid memory alloc request size 1585837200' after upgrading to 17.5
2025-05-22 12:23 UTC Shlok Kyal <shlok.kyal.oss@gmail.com>
` RE: Logical replication 'invalid memory alloc request size 1585837200' after upgrading to 17.5
2025-05-22 12:59 UTC Hayato Kuroda (Fujitsu) <kuroda.hayato@fujitsu.com>
` Re: Logical replication 'invalid memory alloc request size 1585837200' after upgrading to 17.5
2025-05-23 03:00 UTC Amit Kapila <amit.kapila16@gmail.com>
` Re: Logical replication 'invalid memory alloc request size 1585837200' after upgrading to 17.5
2025-05-23 17:31 UTC Masahiko Sawada <sawada.mshk@gmail.com>
` Re: Logical replication 'invalid memory alloc request size 1585837200' after upgrading to 17.5
2025-05-24 15:42 UTC Duncan Sands <duncan.sands@deepbluecap.com>
` RE: Logical replication 'invalid memory alloc request size 1585837200' after upgrading to 17.5
2025-05-25 04:55 UTC Hayato Kuroda (Fujitsu) <kuroda.hayato@fujitsu.com>
` RE: Logical replication 'invalid memory alloc request size 1585837200' after upgrading to 17.5
2025-05-26 09:22 UTC Hayato Kuroda (Fujitsu) <kuroda.hayato@fujitsu.com>
` Re: Logical replication 'invalid memory alloc request size 1585837200' after upgrading to 17.5
2025-05-26 11:18 UTC Amit Kapila <amit.kapila16@gmail.com>
` Re: Logical replication 'invalid memory alloc request size 1585837200' after upgrading to 17.5
2025-05-26 11:47 UTC Christoph Berg <myon@debian.org>
` Re: Logical replication 'invalid memory alloc request size 1585837200' after upgrading to 17.5
2025-05-27 21:05 UTC Masahiko Sawada <sawada.mshk@gmail.com>
` RE: Logical replication 'invalid memory alloc request size 1585837200' after upgrading to 17.5
2025-05-28 12:27 UTC Hayato Kuroda (Fujitsu) <kuroda.hayato@fujitsu.com>
` Re: Logical replication 'invalid memory alloc request size 1585837200' after upgrading to 17.5
2025-05-28 18:51 UTC Masahiko Sawada <sawada.mshk@gmail.com>
` Re: Logical replication 'invalid memory alloc request size 1585837200' after upgrading to 17.5
2025-05-29 05:20 UTC Amit Kapila <amit.kapila16@gmail.com>
` Re: Logical replication 'invalid memory alloc request size 1585837200' after upgrading to 17.5
2025-05-29 06:07 UTC Masahiko Sawada <sawada.mshk@gmail.com>
` RE: Logical replication 'invalid memory alloc request size 1585837200' after upgrading to 17.5
2025-05-29 06:10 UTC Hayato Kuroda (Fujitsu) <kuroda.hayato@fujitsu.com>
` Re: Logical replication 'invalid memory alloc request size 1585837200' after upgrading to 17.5
2025-05-29 08:22 UTC Amit Kapila <amit.kapila16@gmail.com>
` RE: Logical replication 'invalid memory alloc request size 1585837200' after upgrading to 17.5
2025-05-29 12:09 UTC Hayato Kuroda (Fujitsu) <kuroda.hayato@fujitsu.com>
` Re: Logical replication 'invalid memory alloc request size 1585837200' after upgrading to 17.5
2025-05-29 17:26 UTC Masahiko Sawada <sawada.mshk@gmail.com>
` Re: Logical replication 'invalid memory alloc request size 1585837200' after upgrading to 17.5
2025-05-30 04:01 UTC vignesh C <vignesh21@gmail.com>
` Re: Logical replication 'invalid memory alloc request size 1585837200' after upgrading to 17.5
2025-05-30 04:42 UTC Amit Kapila <amit.kapila16@gmail.com>
` Re: Logical replication 'invalid memory alloc request size 1585837200' after upgrading to 17.5
2025-05-30 12:15 UTC vignesh C <vignesh21@gmail.com>
` Re: Logical replication 'invalid memory alloc request size 1585837200' after upgrading to 17.5
2025-05-30 16:45 UTC Masahiko Sawada <sawada.mshk@gmail.com>
` Re: Logical replication 'invalid memory alloc request size 1585837200' after upgrading to 17.5
2025-05-30 17:29 UTC Masahiko Sawada <sawada.mshk@gmail.com>
` Re: Logical replication 'invalid memory alloc request size 1585837200' after upgrading to 17.5
2025-05-31 04:50 UTC Amit Kapila <amit.kapila16@gmail.com>
` Re: Logical replication 'invalid memory alloc request size 1585837200' after upgrading to 17.5
2025-05-31 07:57 UTC vignesh C <vignesh21@gmail.com>
` Re: Logical replication 'invalid memory alloc request size 1585837200' after upgrading to 17.5
2025-06-02 03:13 UTC vignesh C <vignesh21@gmail.com>
` Re: Logical replication 'invalid memory alloc request size 1585837200' after upgrading to 17.5
2025-06-02 07:12 UTC Duncan Sands <duncan.sands@deepbluecap.com>
` Re: Logical replication 'invalid memory alloc request size 1585837200' after upgrading to 17.5
2025-06-02 10:22 UTC vignesh C <vignesh21@gmail.com>
` RE: Logical replication 'invalid memory alloc request size 1585837200' after upgrading to 17.5
2025-06-02 11:35 UTC Hayato Kuroda (Fujitsu) <kuroda.hayato@fujitsu.com>
` Re: Logical replication 'invalid memory alloc request size 1585837200' after upgrading to 17.5
2025-06-02 16:51 UTC Masahiko Sawada <sawada.mshk@gmail.com>
` Re: Logical replication 'invalid memory alloc request size 1585837200' after upgrading to 17.5
2025-06-02 17:19 UTC Masahiko Sawada <sawada.mshk@gmail.com>
` Re: Logical replication 'invalid memory alloc request size 1585837200' after upgrading to 17.5
2025-06-02 18:08 UTC Masahiko Sawada <sawada.mshk@gmail.com>
` Re: Logical replication 'invalid memory alloc request size 1585837200' after upgrading to 17.5
2025-06-03 03:09 UTC Amit Kapila <amit.kapila16@gmail.com>
` Re: Logical replication 'invalid memory alloc request size 1585837200' after upgrading to 17.5
2025-06-03 03:38 UTC Amit Kapila <amit.kapila16@gmail.com>
` Re: Logical replication 'invalid memory alloc request size 1585837200' after upgrading to 17.5
2025-06-03 07:07 UTC vignesh C <vignesh21@gmail.com>
` Re: Logical replication 'invalid memory alloc request size 1585837200' after upgrading to 17.5
2025-06-03 12:24 UTC vignesh C <vignesh21@gmail.com>
` Re: Logical replication 'invalid memory alloc request size 1585837200' after upgrading to 17.5
2025-06-03 19:43 UTC Masahiko Sawada <sawada.mshk@gmail.com>
` Re: Logical replication 'invalid memory alloc request size 1585837200' after upgrading to 17.5
2025-06-04 06:47 UTC vignesh C <vignesh21@gmail.com>
` RE: Logical replication 'invalid memory alloc request size 1585837200' after upgrading to 17.5
2025-06-04 09:20 UTC Hayato Kuroda (Fujitsu) <kuroda.hayato@fujitsu.com>
` Re: Logical replication 'invalid memory alloc request size 1585837200' after upgrading to 17.5
2025-06-04 21:48 UTC Masahiko Sawada <sawada.mshk@gmail.com>
` Re: Logical replication 'invalid memory alloc request size 1585837200' after upgrading to 17.5
2025-06-04 22:06 UTC Masahiko Sawada <sawada.mshk@gmail.com>
` Re: Logical replication 'invalid memory alloc request size 1585837200' after upgrading to 17.5
2025-06-05 06:20 UTC Amit Kapila <amit.kapila16@gmail.com>
` RE: Logical replication 'invalid memory alloc request size 1585837200' after upgrading to 17.5
2025-06-05 06:36 UTC Hayato Kuroda (Fujitsu) <kuroda.hayato@fujitsu.com>
` Re: Logical replication 'invalid memory alloc request size 1585837200' after upgrading to 17.5
2025-06-05 10:28 UTC vignesh C <vignesh21@gmail.com>
` RE: Logical replication 'invalid memory alloc request size 1585837200' after upgrading to 17.5
2025-06-05 11:07 UTC Hayato Kuroda (Fujitsu) <kuroda.hayato@fujitsu.com>
` RE: Logical replication 'invalid memory alloc request size 1585837200' after upgrading to 17.5
2025-06-05 12:14 UTC Hayato Kuroda (Fujitsu) <kuroda.hayato@fujitsu.com>
` Re: Logical replication 'invalid memory alloc request size 1585837200' after upgrading to 17.5
2025-06-05 17:43 UTC Masahiko Sawada <sawada.mshk@gmail.com>
` Re: Logical replication 'invalid memory alloc request size 1585837200' after upgrading to 17.5
2025-06-05 18:49 UTC Masahiko Sawada <sawada.mshk@gmail.com>
` Re: Logical replication 'invalid memory alloc request size 1585837200' after upgrading to 17.5
2025-06-05 19:21 UTC Masahiko Sawada <sawada.mshk@gmail.com>
` Re: Logical replication 'invalid memory alloc request size 1585837200' after upgrading to 17.5
2025-06-05 21:59 UTC Masahiko Sawada <sawada.mshk@gmail.com>
` Re: Logical replication 'invalid memory alloc request size 1585837200' after upgrading to 17.5
2025-06-06 03:21 UTC Amit Kapila <amit.kapila16@gmail.com>
` Re: Logical replication 'invalid memory alloc request size 1585837200' after upgrading to 17.5
2025-06-06 03:43 UTC Amit Kapila <amit.kapila16@gmail.com>
` RE: Logical replication 'invalid memory alloc request size 1585837200' after upgrading to 17.5
2025-06-06 06:22 UTC Hayato Kuroda (Fujitsu) <kuroda.hayato@fujitsu.com>
` RE: Logical replication 'invalid memory alloc request size 1585837200' after upgrading to 17.5
2025-06-06 06:54 UTC Hayato Kuroda (Fujitsu) <kuroda.hayato@fujitsu.com>
` Re: Logical replication 'invalid memory alloc request size 1585837200' after upgrading to 17.5
2025-06-06 17:20 UTC Masahiko Sawada <sawada.mshk@gmail.com>
` Re: Logical replication 'invalid memory alloc request size 1585837200' after upgrading to 17.5
2025-06-06 17:23 UTC Masahiko Sawada <sawada.mshk@gmail.com>
` Re: Logical replication 'invalid memory alloc request size 1585837200' after upgrading to 17.5
2025-06-07 06:03 UTC Amit Kapila <amit.kapila16@gmail.com>
` Re: Logical replication 'invalid memory alloc request size 1585837200' after upgrading to 17.5
2025-06-07 07:17 UTC vignesh C <vignesh21@gmail.com>
` Re: Logical replication 'invalid memory alloc request size 1585837200' after upgrading to 17.5
2025-06-08 13:43 UTC vignesh C <vignesh21@gmail.com>
` Re: Logical replication 'invalid memory alloc request size 1585837200' after upgrading to 17.5
2025-06-10 19:19 UTC Masahiko Sawada <sawada.mshk@gmail.com>
` RE: Logical replication 'invalid memory alloc request size 1585837200' after upgrading to 17.5
2025-06-11 01:45 UTC Hayato Kuroda (Fujitsu) <kuroda.hayato@fujitsu.com>
` Re: Logical replication 'invalid memory alloc request size 1585837200' after upgrading to 17.5
2025-06-11 03:19 UTC Amit Kapila <amit.kapila16@gmail.com>
` Re: Logical replication 'invalid memory alloc request size 1585837200' after upgrading to 17.5
2025-06-11 22:03 UTC Masahiko Sawada <sawada.mshk@gmail.com>
` Re: Logical replication 'invalid memory alloc request size 1585837200' after upgrading to 17.5
2025-06-12 06:47 UTC vignesh C <vignesh21@gmail.com>
` Re: Logical replication 'invalid memory alloc request size 1585837200' after upgrading to 17.5
2025-06-13 23:52 UTC Masahiko Sawada <sawada.mshk@gmail.com>
` Re: Logical replication 'invalid memory alloc request size 1585837200' after upgrading to 17.5
2025-06-16 02:27 UTC vignesh C <vignesh21@gmail.com>
` Re: Logical replication 'invalid memory alloc request size 1585837200' after upgrading to 17.5
2025-06-17 17:40 UTC Masahiko Sawada <sawada.mshk@gmail.com>
` Re: Logical replication 'invalid memory alloc request size 1585837200' after upgrading to 17.5
2025-06-20 05:00 UTC Alexander Lakhin <exclusion@gmail.com>
` Re: Logical replication 'invalid memory alloc request size 1585837200' after upgrading to 17.5
2025-06-20 06:04 UTC vignesh C <vignesh21@gmail.com>
` Re: Logical replication 'invalid memory alloc request size 1585837200' after upgrading to 17.5
2025-06-20 07:48 UTC Duncan Sands <duncan.sands@deepbluecap.com>
` RE: Logical replication 'invalid memory alloc request size 1585837200' after upgrading to 17.5
2025-06-20 08:20 UTC Hayato Kuroda (Fujitsu) <kuroda.hayato@fujitsu.com>
` Re: Logical replication 'invalid memory alloc request size 1585837200' after upgrading to 17.5
2025-06-21 00:17 UTC Masahiko Sawada <sawada.mshk@gmail.com>
` Re: Logical replication 'invalid memory alloc request size 1585837200' after upgrading to 17.5
2025-06-22 02:57 UTC vignesh C <vignesh21@gmail.com>
` Re: Logical replication 'invalid memory alloc request size 1585837200' after upgrading to 17.5
2025-06-23 02:52 UTC Amit Kapila <amit.kapila16@gmail.com>
` Re: Logical replication 'invalid memory alloc request size 1585837200' after upgrading to 17.5
2025-06-23 07:14 UTC Masahiko Sawada <sawada.mshk@gmail.com>
` RE: Logical replication 'invalid memory alloc request size 1585837200' after upgrading to 17.5
2025-06-23 12:03 UTC Hayato Kuroda (Fujitsu) <kuroda.hayato@fujitsu.com>
` Re: Logical replication 'invalid memory alloc request size 1585837200' after upgrading to 17.5
2025-06-23 14:05 UTC Masahiko Sawada <sawada.mshk@gmail.com>
` Re: Logical replication 'invalid memory alloc request size 1585837200' after upgrading to 17.5
2025-06-24 01:24 UTC Masahiko Sawada <sawada.mshk@gmail.com>
` Re: Logical replication 'invalid memory alloc request size 1585837200' after upgrading to 17.5
2025-06-24 03:51 UTC Amit Kapila <amit.kapila16@gmail.com>
` Re: Logical replication 'invalid memory alloc request size 1585837200' after upgrading to 17.5
2025-06-24 04:18 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: Logical replication 'invalid memory alloc request size 1585837200' after upgrading to 17.5
2025-06-24 04:22 UTC Masahiko Sawada <sawada.mshk@gmail.com>
` Re: Logical replication 'invalid memory alloc request size 1585837200' after upgrading to 17.5
2025-06-24 04:34 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: Logical replication 'invalid memory alloc request size 1585837200' after upgrading to 17.5
2025-06-24 04:58 UTC Michael Paquier <michael@paquier.xyz>
` Re: Logical replication 'invalid memory alloc request size 1585837200' after upgrading to 17.5
2025-06-24 05:14 UTC Masahiko Sawada <sawada.mshk@gmail.com>
` Re: Logical replication 'invalid memory alloc request size 1585837200' after upgrading to 17.5
2025-07-02 06:32 UTC Masahiko Sawada <sawada.mshk@gmail.com>
[94+ messages in thread]
[PATCH v1 1/1] Remove xl_commit_ts_set.
2025-07-02 00:45 UTC Andy Fan <zhihuifan1213@163.com>
BUG #18973: The default enable_material=ON affects the cost estimation of optimizer, resulting in 10968x slow
2025-06-30 13:44 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18973: The default enable_material=ON affects the cost estimation of optimizer, resulting in 10968x slow
2025-06-30 14:56 UTC Tom Lane <tgl@sss.pgh.pa.us>
[2+ messages in thread]
Logical replication 'ERROR: invalid memory alloc request size 1831213792' after upgrading to 15.13
2025-06-09 12:10 UTC Braulio Fdo Gonzalez <brauliofg@gmail.com>
` RE: Logical replication 'ERROR: invalid memory alloc request size 1831213792' after upgrading to 15.13
2025-06-10 02:09 UTC Hayato Kuroda (Fujitsu) <kuroda.hayato@fujitsu.com>
` Re: Logical replication 'ERROR: invalid memory alloc request size 1831213792' after upgrading to 15.13
2025-06-17 17:45 UTC Masahiko Sawada <sawada.mshk@gmail.com>
` Re: Logical replication 'ERROR: invalid memory alloc request size 1831213792' after upgrading to 15.13
2025-06-29 03:29 UTC Braulio Fdo Gonzalez <brauliofg@gmail.com>
` Re: Logical replication 'ERROR: invalid memory alloc request size 1831213792' after upgrading to 15.13
2025-06-30 03:40 UTC Masahiko Sawada <sawada.mshk@gmail.com>
[5+ messages in thread]
BUG #18971: Server passes an invalid (indirect) path in PGDATA to the external program
2025-06-28 07:17 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18971: Server passes an invalid (indirect) path in PGDATA to the external program
2025-06-28 19:13 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #18971: Server passes an invalid (indirect) path in PGDATA to the external program
2025-06-28 19:32 UTC Dmitry Kovalenko <d.kovalenko@postgrespro.ru>
` Re: BUG #18971: Server passes an invalid (indirect) path in PGDATA to the external program
2025-06-28 20:19 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #18971: Server passes an invalid (indirect) path in PGDATA to the external program
2025-06-28 21:12 UTC David G. Johnston <david.g.johnston@gmail.com>
` Re: BUG #18971: Server passes an invalid (indirect) path in PGDATA to the external program
2025-06-29 06:00 UTC Laurenz Albe <laurenz.albe@cybertec.at>
[6+ messages in thread]
BUG #18953: Planner fails to build plan for complex query with LATERAL references
2025-06-10 18:00 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18953: Planner fails to build plan for complex query with LATERAL references
2025-06-11 08:33 UTC Richard Guo <guofenglinux@gmail.com>
` Re: BUG #18953: Planner fails to build plan for complex query with LATERAL references
2025-06-11 13:28 UTC Richard Guo <guofenglinux@gmail.com>
` Re: BUG #18953: Planner fails to build plan for complex query with LATERAL references
2025-06-12 21:50 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #18953: Planner fails to build plan for complex query with LATERAL references
2025-06-13 20:58 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #18953: Planner fails to build plan for complex query with LATERAL references
2025-06-16 07:22 UTC Richard Guo <guofenglinux@gmail.com>
` Re: BUG #18953: Planner fails to build plan for complex query with LATERAL references
2025-06-16 15:24 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #18953: Planner fails to build plan for complex query with LATERAL references
2025-06-17 02:20 UTC Richard Guo <guofenglinux@gmail.com>
` Re: BUG #18953: Planner fails to build plan for complex query with LATERAL references
2025-06-17 16:29 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #18953: Planner fails to build plan for complex query with LATERAL references
2025-06-22 12:00 UTC Alexander Lakhin <exclusion@gmail.com>
` Re: BUG #18953: Planner fails to build plan for complex query with LATERAL references
2025-06-22 18:31 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #18953: Planner fails to build plan for complex query with LATERAL references
2025-06-23 09:13 UTC Richard Guo <guofenglinux@gmail.com>
` Re: BUG #18953: Planner fails to build plan for complex query with LATERAL references
2025-06-23 18:24 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #18953: Planner fails to build plan for complex query with LATERAL references
2025-06-24 07:00 UTC Alexander Lakhin <exclusion@gmail.com>
` Re: BUG #18953: Planner fails to build plan for complex query with LATERAL references
2025-06-26 18:37 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #18953: Planner fails to build plan for complex query with LATERAL references
2025-06-27 06:08 UTC Richard Guo <guofenglinux@gmail.com>
` Re: BUG #18953: Planner fails to build plan for complex query with LATERAL references
2025-06-27 06:29 UTC Richard Guo <guofenglinux@gmail.com>
` Re: BUG #18953: Planner fails to build plan for complex query with LATERAL references
2025-06-27 18:35 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #18953: Planner fails to build plan for complex query with LATERAL references
2025-06-27 21:37 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #18953: Planner fails to build plan for complex query with LATERAL references
2025-06-28 06:00 UTC Alexander Lakhin <exclusion@gmail.com>
` Re: BUG #18953: Planner fails to build plan for complex query with LATERAL references
2025-06-28 18:26 UTC Tom Lane <tgl@sss.pgh.pa.us>
[21+ messages in thread]
PGXS does not properly uninstall documentation
2025-05-15 17:25 UTC Karl O. Pinc <kop@karlpinc.com>
` Re: PGXS does not properly uninstall documentation
2025-06-25 14:42 UTC Karl O. Pinc <kop@karlpinc.com>
` Re: PGXS does not properly uninstall documentation
2025-06-27 21:06 UTC Tom Lane <tgl@sss.pgh.pa.us>
[3+ messages in thread]
BUG #18968: GiST Index Cost Estimation
2025-06-24 23:00 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18968: GiST Index Cost Estimation
2025-06-27 21:03 UTC Tom Lane <tgl@sss.pgh.pa.us>
[2+ messages in thread]
[PATCH v3 1/1] Allow resetting unknown custom GUCs with reserved prefixes.
2025-06-25 15:54 UTC Nathan Bossart <nathan@postgresql.org>
` [PATCH v2 1/1] Allow resetting unknown custom GUCs with reserved prefixes.
2025-06-25 15:54 UTC Nathan Bossart <nathan@postgresql.org>
` [PATCH v4 1/1] Allow resetting unknown custom GUCs with reserved prefixes.
2025-06-25 15:54 UTC Nathan Bossart <nathan@postgresql.org>
[3+ messages in thread]
BUG #18966: Invalid SQL queries hang indefinitely until server restart
2025-06-24 14:10 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18966: Invalid SQL queries hang indefinitely until server restart
2025-06-24 19:09 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #18966: Invalid SQL queries hang indefinitely until server restart
2025-06-25 05:36 UTC Laurenz Albe <laurenz.albe@cybertec.at>
` Re: BUG #18966: Invalid SQL queries hang indefinitely until server restart
2025-06-25 14:23 UTC Jérémy Spriet <jeremy.spriet@gmail.com>
[4+ messages in thread]
BUG #18969: security tests failures
2025-06-25 06:15 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18969: security tests failures
2025-06-25 12:31 UTC Daniel Gustafsson <daniel@yesql.se>
[2+ messages in thread]
BUG #18509: Logical decoding behaves badly when processing a change record for a table with altered column
2024-06-14 18:00 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18509: Logical decoding behaves badly when processing a change record for a table with altered column
2024-07-07 11:00 UTC Alexander Lakhin <exclusion@gmail.com>
` Re: BUG #18509: Logical decoding behaves badly when processing a change record for a table with altered column
2025-06-24 00:20 UTC Ajin Cherian <itsajin@gmail.com>
[3+ messages in thread]
Index Rebuild Bug fixed in 14.6.7
2025-06-20 20:21 UTC Kumar Boinpalli <pammi.boinpalli@gmail.com>
` Re: Index Rebuild Bug fixed in 14.6.7
2025-06-20 20:41 UTC Bruce Momjian <bruce@momjian.us>
[2+ messages in thread]
BUG #18963: Column confupdsetcols missing in pg_catalog.pg_constraint
2025-06-19 16:33 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18963: Column confupdsetcols missing in pg_catalog.pg_constraint
2025-06-20 15:14 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #18963: Column confupdsetcols missing in pg_catalog.pg_constraint
2025-06-20 20:35 UTC Mathias Panzenböck <grosser.meister.morti@gmx.net>
[3+ messages in thread]
BUG #18962: Type Conversion incorrect when performing UNION of queries.
2025-06-19 12:21 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18962: Type Conversion incorrect when performing UNION of queries.
2025-06-19 15:44 UTC Tom Lane <tgl@sss.pgh.pa.us>
` BUG #18962: Type Conversion incorrect when performing UNION of queries.
2025-06-19 15:46 UTC David G. Johnston <david.g.johnston@gmail.com>
` Re: BUG #18962: Type Conversion incorrect when performing UNION of queries.
2025-06-20 05:39 UTC Sundar Mudupalli <sundar@mudupalli.com>
[4+ messages in thread]
AW: [EXTERNAL] Re: BUG #18959: Name collisions of expression indexes during parallel Index creations on a pratitioned table.
2025-06-19 14:08 UTC Chrzan, Maximilian <maximilian.chrzan@here.com>
[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