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-10-21T12:21:08Z Version 18.0 of postgres image in dockerhub - container crashes when starting up Yuval Roth <yuvalroth123@gmail.com>
2025-10-21T11:22:32Z Re: Segfault in RI UPDATE CASCADE on partitioned tables with LIKE+ATTACH child (attnum drift) Has attachments David Rowley <dgrowleyml@gmail.com>
2025-10-21T09:11:51Z Re: Segfault in RI UPDATE CASCADE on partitioned tables with LIKE+ATTACH child (attnum drift) Has attachments Amit Langote <amitlangote09@gmail.com>
2025-10-21T08:21:24Z Re: postgres access violation in pg_detoast_datum Álvaro Herrera <alvherre@kurilemu.de>
2025-10-21T08:15:29Z TLS verification to intermediate trust anchor with psql Miroslav Pankov <miroslav.pankov@broadcom.com>
2025-10-21T07:43:58Z BUG #19092: scram_free() will free on address which was not malloc()-ed in pg_scram_mech PG Bug reporting form <noreply@postgresql.org>
2025-10-21T07:05:09Z Re: postgres access violation in pg_detoast_datum David Rowley <dgrowleyml@gmail.com>
2025-10-21T06:49:13Z postgres access violation in pg_detoast_datum Has attachments Arnd Empting <arnd.empting@koerber.com>
2025-10-21T05:20:31Z Re: Segfault in RI UPDATE CASCADE on partitioned tables with LIKE+ATTACH child (attnum drift) Has attachments David Rowley <dgrowleyml@gmail.com>
2025-10-21T01:28:22Z Re: Segfault in RI UPDATE CASCADE on partitioned tables with LIKE+ATTACH child (attnum drift) Has attachments Amit Langote <amitlangote09@gmail.com>
2025-10-21T00:44:52Z Re: Potential "AIO / io workers" inter-worker locking issue in PG18? David Rowley <dgrowleyml@gmail.com>
2025-10-20T22:46:40Z Re: Potential "AIO / io workers" inter-worker locking issue in PG18? Marco Boeringa <marco@boeringa.demon.nl>
2025-10-20T22:16:13Z Re: Potential "AIO / io workers" inter-worker locking issue in PG18? David Rowley <dgrowleyml@gmail.com>
2025-10-20T21:57:54Z Re: Potential "AIO / io workers" inter-worker locking issue in PG18? Marco Boeringa <marco@boeringa.demon.nl>
2025-10-20T21:06:51Z Re: Potential "AIO / io workers" inter-worker locking issue in PG18? David Rowley <dgrowleyml@gmail.com>
2025-10-20T20:02:35Z Re: Potential "AIO / io workers" inter-worker locking issue in PG18? Marco Boeringa <marco@boeringa.demon.nl>
2025-10-20T19:27:47Z Re: Segfault in RI UPDATE CASCADE on partitioned tables with LIKE+ATTACH child (attnum drift) David Rowley <dgrowleyml@gmail.com>
2025-10-20T19:09:30Z Re: Potential "AIO / io workers" inter-worker locking issue in PG18? David Rowley <dgrowleyml@gmail.com>
2025-10-20T17:18:12Z Re: PG17.6 wal apply bug (SIGSEGV) Peter Geoghegan <pg@bowt.ie>
2025-10-20T16:34:14Z Re: PG17.6 wal apply bug (SIGSEGV) "badfilez@gmail.com" <badfilez@gmail.com>
2025-10-20T14:42:32Z Re: Potential "AIO / io workers" inter-worker locking issue in PG18? Marco Boeringa <marco@boeringa.demon.nl>
2025-10-20T13:48:40Z Re: Segfault in RI UPDATE CASCADE on partitioned tables with LIKE+ATTACH child (attnum drift) Has attachments Amit Langote <amitlangote09@gmail.com>
2025-10-20T11:22:45Z Re: Potential "AIO / io workers" inter-worker locking issue in PG18? Marco Boeringa <marco@boeringa.demon.nl>
2025-10-20T11:14:29Z Re: PATCH for BUG #18785: Pointer bmr.rel, dereferenced by passing as 1st parameter to function is checked for NULL later Nikolay Shaplov <dhyan@nataraj.su>
2025-10-20T09:34:19Z Re: Potential "AIO / io workers" inter-worker locking issue in PG18? Marco Boeringa <marco@boeringa.demon.nl>