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-09-29T12:36:15Z Cast to regrole on a literal string in a PL/pgSQL function LEMAIRE Leslie (Chargée de mission) - SG/DNUM/UNI/DRC <leslie.lemaire@developpement-durable.gouv.fr>
2025-09-29T01:50:19Z Re: The issue of incorrect width estimation in UNION queries David Rowley <dgrowleyml@gmail.com>
2025-09-28T23:47:52Z Re: BUG #19062: PostgreSQL 12.22 does not compile because of conflicting types for CollationCreate Thomas Munro <thomas.munro@gmail.com>
2025-09-28T08:55:45Z Re: TRAP: failed Assert("outerPlan != NULL") in postgres_fdw.c Etsuro Fujita <etsuro.fujita@gmail.com>
2025-09-27T09:07:15Z Re: BUG #19067: On master at commit 66cdef4425f3, "psql -c 'select 1' dbname" causes the backend to seg fault David Rowley <dgrowleyml@gmail.com>
2025-09-26T19:50:40Z BUG #19067: On master at commit 66cdef4425f3, "psql -c 'select 1' dbname" causes the backend to seg fault PG Bug reporting form <noreply@postgresql.org>
2025-09-26T17:02:38Z Re: Postgres: Queries are too slow after upgrading to PG17 from PG15 Peter Geoghegan <pg@bowt.ie>
2025-09-26T14:53:26Z Re: BUG #19066: postgresql-18.0/src/backend/optimizer/geqo/geqo_ox2.c:86: Array index check in wrong place ? Tom Lane <tgl@sss.pgh.pa.us>
2025-09-26T13:35:50Z Re: BUG #19064: Trigger allows creation with invalid column references but fails at runtime Anthony Sotolongo <asotolongo@gmail.com>
2025-09-26T13:34:38Z Re: TRAP: failed Assert("outerPlan != NULL") in postgres_fdw.c Álvaro Herrera <alvherre@kurilemu.de>
2025-09-26T12:59:45Z Re: BUG #19064: Trigger allows creation with invalid column references but fails at runtime Rahila Syed <rahilasyed90@gmail.com>
2025-09-26T12:46:03Z Re: BUG #19064: Trigger allows creation with invalid column references but fails at runtime "David G. Johnston" <david.g.johnston@gmail.com>
2025-09-26T12:30:36Z Re: Postgres: Queries are too slow after upgrading to PG17 from PG15 Todd Cook <cookt@blackduck.com>
2025-09-26T09:51:09Z BUG #19066: postgresql-18.0/src/backend/optimizer/geqo/geqo_ox2.c:86: Array index check in wrong place ? PG Bug reporting form <noreply@postgresql.org>
2025-09-26T09:48:20Z BUG #19065: postgresql-18.0/src/bin/pg_combinebackup/reconstruct.c:230: Array sanity check in wrong place ? PG Bug reporting form <noreply@postgresql.org>
2025-09-26T09:20:45Z Re: BUG #19007: Planner fails to choose partial index with spurious 'not null' Has attachments Richard Guo <guofenglinux@gmail.com>
2025-09-26T09:14:08Z Re: Issue with PostgreSQL 18.0 Docker image volume mount (/var/lib/postgresql/data symlink) Magnus Hagander <magnus@hagander.net>
2025-09-26T07:36:24Z BUG #19064: Trigger allows creation with invalid column references but fails at runtime PG Bug reporting form <noreply@postgresql.org>
2025-09-26T05:53:09Z Issue with PostgreSQL 18.0 Docker image volume mount (/var/lib/postgresql/data symlink) Pavel Hushcha <paul.fastest@gmail.com>
2025-09-25T21:42:19Z Re: The issue of incorrect width estimation in UNION queries Has attachments David Rowley <dgrowleyml@gmail.com>
2025-09-25T19:46:44Z Re: Postgres: Queries are too slow after upgrading to PG17 from PG15 Peter Geoghegan <pg@bowt.ie>
2025-09-25T19:28:34Z Re: Postgres: Queries are too slow after upgrading to PG17 from PG15 Todd Cook <cookt@blackduck.com>
2025-09-25T18:45:41Z Re: Postgres: Queries are too slow after upgrading to PG17 from PG15 Peter Geoghegan <pg@bowt.ie>
2025-09-25T18:07:11Z Re: Postgres: Queries are too slow after upgrading to PG17 from PG15 Todd Cook <cookt@blackduck.com>
2025-09-25T10:55:44Z Re: TRAP: failed Assert("outerPlan != NULL") in postgres_fdw.c Etsuro Fujita <etsuro.fujita@gmail.com>