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-05-31T18:22:08Z Re: [bug] keyword commit being accepted for column name Kirk Parker <khp@equatoria.us>
2025-05-31T18:03:09Z [bug] keyword commit being accepted for column name Vinícius Abrahão <vinnix.bsd@gmail.com>
2025-05-31T07:57:52Z Re: Logical replication 'invalid memory alloc request size 1585837200' after upgrading to 17.5 Has attachments vignesh C <vignesh21@gmail.com>
2025-05-31T04:50:45Z Re: Logical replication 'invalid memory alloc request size 1585837200' after upgrading to 17.5 Amit Kapila <amit.kapila16@gmail.com>
2025-05-30T21:14:26Z Re: BUG #18941: PostgreSQL planner does not select a multicolumn btree_gin index under RLS Pepe Fagoaga <pepe@prowler.com>
2025-05-30T20:37:15Z Re: BUG #18941: PostgreSQL planner does not select a multicolumn btree_gin index under RLS Tom Lane <tgl@sss.pgh.pa.us>
2025-05-30T20:02:50Z Re: BUG #18942: walsender memory allocation failure adding snapshot and invalidations to logical replica w/PG 16.9 Masahiko Sawada <sawada.mshk@gmail.com>
2025-05-30T19:43:34Z BUG #18942: walsender memory allocation failure adding snapshot and invalidations to logical replica w/PG 16.9 PG Bug reporting form <noreply@postgresql.org>
2025-05-30T19:39:43Z BUG #18941: PostgreSQL planner does not select a multicolumn btree_gin index under RLS PG Bug reporting form <noreply@postgresql.org>
2025-05-30T17:29:34Z Re: Logical replication 'invalid memory alloc request size 1585837200' after upgrading to 17.5 Masahiko Sawada <sawada.mshk@gmail.com>
2025-05-30T16:59:58Z Re: [EXT] Re: GSS Auth issue when user member of lots of AD groups Tom Lane <tgl@sss.pgh.pa.us>
2025-05-30T16:45:34Z Re: Logical replication 'invalid memory alloc request size 1585837200' after upgrading to 17.5 Masahiko Sawada <sawada.mshk@gmail.com>
2025-05-30T12:15:19Z Re: Logical replication 'invalid memory alloc request size 1585837200' after upgrading to 17.5 Has attachments vignesh C <vignesh21@gmail.com>
2025-05-30T09:27:21Z RE: [EXT] Re: GSS Auth issue when user member of lots of AD groups Chris Gooch <cgooch@bamfunds.com>
2025-05-30T04:42:16Z Re: Logical replication 'invalid memory alloc request size 1585837200' after upgrading to 17.5 Amit Kapila <amit.kapila16@gmail.com>
2025-05-30T04:01:19Z Re: Logical replication 'invalid memory alloc request size 1585837200' after upgrading to 17.5 vignesh C <vignesh21@gmail.com>
2025-05-29T23:32:05Z Re: Standby server with cascade logical replication could not be properly stopped under load Michael Paquier <michael@paquier.xyz>
2025-05-29T23:17:16Z Re: [EXT] Re: GSS Auth issue when user member of lots of AD groups Jacob Champion <jacob.champion@enterprisedb.com>
2025-05-29T18:41:51Z Re: [EXT] Re: GSS Auth issue when user member of lots of AD groups Tom Lane <tgl@sss.pgh.pa.us>
2025-05-29T18:40:28Z Re: [EXT] Re: GSS Auth issue when user member of lots of AD groups Jacob Champion <jacob.champion@enterprisedb.com>
2025-05-29T18:09:18Z Re: [EXT] Re: GSS Auth issue when user member of lots of AD groups Has attachments Tom Lane <tgl@sss.pgh.pa.us>
2025-05-29T17:26:32Z Re: Logical replication 'invalid memory alloc request size 1585837200' after upgrading to 17.5 Masahiko Sawada <sawada.mshk@gmail.com>
2025-05-29T16:59:18Z BUG #18940: PostgreSQL 18beta1 fails 'collate.windows.win1252' regression when building with MSYS/mingw PG Bug reporting form <noreply@postgresql.org>
2025-05-29T12:09:57Z RE: Logical replication 'invalid memory alloc request size 1585837200' after upgrading to 17.5 Has attachments "Hayato Kuroda (Fujitsu)" <kuroda.hayato@fujitsu.com>
2025-05-29T10:28:01Z Re: Standby server with cascade logical replication could not be properly stopped under load Ajin Cherian <itsajin@gmail.com>