Horton
Menu

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-26T18:37:57Z Re: BUG #18953: Planner fails to build plan for complex query with LATERAL references Tom Lane <tgl@sss.pgh.pa.us>
2025-06-25T16:06:05Z Re: BUG #18964: `ALTER DATABASE ... RESET ...` fails to reset extension parameters that no longer exist Has attachments Nathan Bossart <nathandbossart@gmail.com>
2025-06-25T15:54:33Z [PATCH v4 1/1] Allow resetting unknown custom GUCs with reserved prefixes. Nathan Bossart <nathan@postgresql.org>
2025-06-25T15:54:33Z [PATCH v3 1/1] Allow resetting unknown custom GUCs with reserved prefixes. Nathan Bossart <nathan@postgresql.org>
2025-06-25T15:54:33Z [PATCH v2 1/1] Allow resetting unknown custom GUCs with reserved prefixes. Nathan Bossart <nathan@postgresql.org>
2025-06-25T14:42:06Z Re: PGXS does not properly uninstall documentation "Karl O. Pinc" <kop@karlpinc.com>
2025-06-25T14:23:01Z Re: BUG #18966: Invalid SQL queries hang indefinitely until server restart Jérémy Spriet <jeremy.spriet@gmail.com>
2025-06-25T12:31:59Z Re: BUG #18969: security tests failures Daniel Gustafsson <daniel@yesql.se>
2025-06-25T06:15:23Z BUG #18969: security tests failures PG Bug reporting form <noreply@postgresql.org>
2025-06-25T05:36:35Z Re: BUG #18966: Invalid SQL queries hang indefinitely until server restart Laurenz Albe <laurenz.albe@cybertec.at>
2025-06-25T04:04:10Z Re: BUG #16961: Could not access status of transaction Daniil Davydov <3danissimo@gmail.com>
2025-06-24T23:00:41Z BUG #18968: GiST Index Cost Estimation PG Bug reporting form <noreply@postgresql.org>
2025-06-24T19:09:13Z Re: BUG #18966: Invalid SQL queries hang indefinitely until server restart Tom Lane <tgl@sss.pgh.pa.us>
2025-06-24T14:10:08Z BUG #18966: Invalid SQL queries hang indefinitely until server restart PG Bug reporting form <noreply@postgresql.org>
2025-06-24T07:00:00Z Re: BUG #18953: Planner fails to build plan for complex query with LATERAL references Alexander Lakhin <exclusion@gmail.com>
2025-06-24T05:14:41Z Re: Logical replication 'invalid memory alloc request size 1585837200' after upgrading to 17.5 Has attachments Masahiko Sawada <sawada.mshk@gmail.com>
2025-06-24T04:58:43Z Re: Logical replication 'invalid memory alloc request size 1585837200' after upgrading to 17.5 Michael Paquier <michael@paquier.xyz>
2025-06-24T04:34:26Z Re: Logical replication 'invalid memory alloc request size 1585837200' after upgrading to 17.5 Tom Lane <tgl@sss.pgh.pa.us>
2025-06-24T04:22:53Z Re: Logical replication 'invalid memory alloc request size 1585837200' after upgrading to 17.5 Masahiko Sawada <sawada.mshk@gmail.com>
2025-06-24T04:18:45Z Re: Logical replication 'invalid memory alloc request size 1585837200' after upgrading to 17.5 Tom Lane <tgl@sss.pgh.pa.us>
2025-06-24T03:51:06Z Re: Logical replication 'invalid memory alloc request size 1585837200' after upgrading to 17.5 Amit Kapila <amit.kapila16@gmail.com>
2025-06-24T01:24:03Z Re: Logical replication 'invalid memory alloc request size 1585837200' after upgrading to 17.5 Has attachments Masahiko Sawada <sawada.mshk@gmail.com>
2025-06-24T00:20:06Z Re: BUG #18509: Logical decoding behaves badly when processing a change record for a table with altered column Has attachments Ajin Cherian <itsajin@gmail.com>
2025-06-23T18:24:01Z 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-23T14:05:35Z Re: Logical replication 'invalid memory alloc request size 1585837200' after upgrading to 17.5 Masahiko Sawada <sawada.mshk@gmail.com>