Messages in pgsql-bugs

Same data as JSON: GET /api/v1/messages same messages as JSON; filter by `list`, `from`/`to`. API reference →
Date ▼ SubjectFrom
2025-06-23T12:03:33Z RE: Logical replication 'invalid memory alloc request size 1585837200' after upgrading to 17.5 "Hayato Kuroda (Fujitsu)" <kuroda.hayato@fujitsu.com>
2025-06-23T09:13:49Z Re: BUG #18953: Planner fails to build plan for complex query with LATERAL references Richard Guo <guofenglinux@gmail.com>
2025-06-23T07:14:45Z Re: Logical replication 'invalid memory alloc request size 1585837200' after upgrading to 17.5 Masahiko Sawada <sawada.mshk@gmail.com>
2025-06-23T02:52:45Z Re: Logical replication 'invalid memory alloc request size 1585837200' after upgrading to 17.5 Amit Kapila <amit.kapila16@gmail.com>
2025-06-22T18:31:56Z Re: BUG #18953: Planner fails to build plan for complex query with LATERAL references Has attachments Tom Lane <tgl@sss.pgh.pa.us>
2025-06-22T12:00:01Z Re: BUG #18953: Planner fails to build plan for complex query with LATERAL references Alexander Lakhin <exclusion@gmail.com>
2025-06-22T02:57:49Z Re: Logical replication 'invalid memory alloc request size 1585837200' after upgrading to 17.5 vignesh C <vignesh21@gmail.com>
2025-06-21T21:46:18Z Re: BUG #18960: Mistake in test test_simple_pipeline (libpq_pipeline.c) Tom Lane <tgl@sss.pgh.pa.us>
2025-06-21T20:42:42Z Re: BUG #18960: Mistake in test test_simple_pipeline (libpq_pipeline.c) Dmitry Kovalenko <d.kovalenko@postgrespro.ru>
2025-06-21T20:01:03Z Re: BUG #18960: Mistake in test test_simple_pipeline (libpq_pipeline.c) Has attachments Tom Lane <tgl@sss.pgh.pa.us>
2025-06-21T00:17:32Z Re: Logical replication 'invalid memory alloc request size 1585837200' after upgrading to 17.5 Masahiko Sawada <sawada.mshk@gmail.com>
2025-06-20T22:48:37Z Re: BUG #18964: `ALTER DATABASE ... RESET ...` fails to reset extension parameters that no longer exist Has attachments Nathan Bossart <nathandbossart@gmail.com>
2025-06-20T21:20:25Z Re: BUG #18964: `ALTER DATABASE ... RESET ...` fails to reset extension parameters that no longer exist Nathan Bossart <nathandbossart@gmail.com>
2025-06-20T20:41:16Z Re: Index Rebuild Bug fixed in 14.6.7 Bruce Momjian <bruce@momjian.us>
2025-06-20T20:35:40Z Re: BUG #18963: Column confupdsetcols missing in pg_catalog.pg_constraint Mathias Panzenböck <grosser.meister.morti@gmx.net>
2025-06-20T20:24:41Z Re: BUG #18964: `ALTER DATABASE ... RESET ...` fails to reset extension parameters that no longer exist Tom Lane <tgl@sss.pgh.pa.us>
2025-06-20T20:21:19Z Index Rebuild Bug fixed in 14.6.7 Kumar Boinpalli <pammi.boinpalli@gmail.com>
2025-06-20T19:53:43Z Re: BUG #18964: `ALTER DATABASE ... RESET ...` fails to reset extension parameters that no longer exist Nathan Bossart <nathandbossart@gmail.com>
2025-06-20T18:37:10Z Re: BUG #18965: Issue with Short-Circuit Evaluation in Boolean Expressions Tom Lane <tgl@sss.pgh.pa.us>
2025-06-20T18:14:22Z Re: BUG #18965: Issue with Short-Circuit Evaluation in Boolean Expressions "David G. Johnston" <david.g.johnston@gmail.com>
2025-06-20T17:50:41Z Re: BUG #18959: Name collisions of expression indexes during parallel Index creations on a pratitioned table. Tom Lane <tgl@sss.pgh.pa.us>
2025-06-20T17:42:06Z BUG #18965: Issue with Short-Circuit Evaluation in Boolean Expressions PG Bug reporting form <noreply@postgresql.org>
2025-06-20T15:14:59Z Re: BUG #18963: Column confupdsetcols missing in pg_catalog.pg_constraint Tom Lane <tgl@sss.pgh.pa.us>
2025-06-20T12:24:20Z BUG #18964: `ALTER DATABASE ... RESET ...` fails to reset extension parameters that no longer exist PG Bug reporting form <noreply@postgresql.org>
2025-06-20T11:29:10Z Re: BUG #18959: Name collisions of expression indexes during parallel Index creations on a pratitioned table. Dilip Kumar <dilipbalaut@gmail.com>