Horton

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-09T15:44:15Z BUG #19081: Inconsistent target rows seen by the UPDATE and INSERT statements within the same transaction PG Bug reporting form <noreply@postgresql.org>
2025-10-09T13:39:38Z BUG #19080: CancelRequest message documentation bug PG Bug reporting form <noreply@postgresql.org>
2025-10-09T12:05:02Z Re: BUG #19079: can't dowmload documentation download aborted Daniel Gustafsson <daniel@yesql.se>
2025-10-09T11:43:01Z BUG #19079: can't dowmload documentation download aborted PG Bug reporting form <noreply@postgresql.org>
2025-10-09T08:35:24Z BUG #19078: Segfaults in tts_minimal_store_tuple() following pg_upgrade PG Bug reporting form <noreply@postgresql.org>
2025-10-09T07:40:03Z Re: Potential "AIO / io workers" inter-worker locking issue in PG18? Marco Boeringa <marco@boeringa.demon.nl>
2025-10-09T02:16:15Z Re: TRAP: failed Assert("outerPlan != NULL") in postgres_fdw.c Michael Paquier <michael@paquier.xyz>
2025-10-08T20:22:48Z Re: Potential "AIO / io workers" inter-worker locking issue in PG18? Marco Boeringa <marco@boeringa.demon.nl>
2025-10-08T20:09:04Z Re: Potential "AIO / io workers" inter-worker locking issue in PG18? Marco Boeringa <marco@boeringa.demon.nl>
2025-10-08T19:08:28Z Re: Potential "AIO / io workers" inter-worker locking issue in PG18? Andres Freund <andres@anarazel.de>
2025-10-08T17:46:42Z Re: Potential "AIO / io workers" inter-worker locking issue in PG18? Marco Boeringa <marco@boeringa.demon.nl>
2025-10-08T13:07:45Z Re: Potential "AIO / io workers" inter-worker locking issue in PG18? Andres Freund <andres@anarazel.de>
2025-10-08T13:04:03Z Re: Potential "AIO / io workers" inter-worker locking issue in PG18? Andres Freund <andres@anarazel.de>
2025-10-08T12:13:28Z Re: Potential "AIO / io workers" inter-worker locking issue in PG18? Marco Boeringa <marco@boeringa.demon.nl>
2025-10-08T11:41:03Z Re: BUG #19076: Generic query plan is extremely slow Laurenz Albe <laurenz.albe@cybertec.at>
2025-10-08T11:17:03Z Re: BUG #19076: Generic query plan is extremely slow Premal Patel <premal.patel@veeva.com>
2025-10-08T10:04:20Z Re: Potential "AIO / io workers" inter-worker locking issue in PG18? Marco Boeringa <marco@boeringa.demon.nl>
2025-10-08T09:13:54Z Re: BUG #19076: Generic query plan is extremely slow David Rowley <dgrowleyml@gmail.com>
2025-10-08T08:21:16Z Re: BUG #19076: Generic query plan is extremely slow Laurenz Albe <laurenz.albe@cybertec.at>
2025-10-08T07:49:04Z Re: Potential "AIO / io workers" inter-worker locking issue in PG18? Marco Boeringa <marco@boeringa.demon.nl>
2025-10-08T06:09:52Z Re: TRAP: failed Assert("outerPlan != NULL") in postgres_fdw.c Etsuro Fujita <etsuro.fujita@gmail.com>
2025-10-08T00:05:56Z Re: TRAP: failed Assert("outerPlan != NULL") in postgres_fdw.c Michael Paquier <michael@paquier.xyz>
2025-10-07T23:17:06Z Re: Potential "AIO / io workers" inter-worker locking issue in PG18? Andres Freund <andres@anarazel.de>
2025-10-07T23:03:40Z Re: Potential "AIO / io workers" inter-worker locking issue in PG18? Andres Freund <andres@anarazel.de>
2025-10-07T22:13:34Z Re: Potential "AIO / io workers" inter-worker locking issue in PG18? Marco Boeringa <marco@boeringa.demon.nl>