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-07-31T02:49:16Z Re: Postgres: Queries are too slow after upgrading to PG17 from PG15 David Rowley <dgrowleyml@gmail.com>
2025-07-31T02:39:31Z Re: Postgres: Queries are too slow after upgrading to PG17 from PG15 Has attachments David Rowley <dgrowleyml@gmail.com>
2025-07-30T21:38:16Z Re: BUG #19003: A SELECT that does not return a valid table "David G. Johnston" <david.g.johnston@gmail.com>
2025-07-30T21:34:41Z Re: BUG #19003: A SELECT that does not return a valid table Tom Lane <tgl@sss.pgh.pa.us>
2025-07-30T20:14:25Z Re: Postgres: Queries are too slow after upgrading to PG17 from PG15 Peter Geoghegan <pg@bowt.ie>
2025-07-30T19:50:10Z Re: Postgres: Queries are too slow after upgrading to PG17 from PG15 Peter Geoghegan <pg@bowt.ie>
2025-07-30T19:48:55Z Re: Postgres: Queries are too slow after upgrading to PG17 from PG15 Todd Cook <cookt@blackduck.com>
2025-07-30T19:20:14Z BUG #19003: A SELECT that does not return a valid table PG Bug reporting form <noreply@postgresql.org>
2025-07-30T19:16:42Z Re: Postgres: Queries are too slow after upgrading to PG17 from PG15 Peter Geoghegan <pg@bowt.ie>
2025-07-30T19:13:16Z Re: BUG #18964: `ALTER DATABASE ... RESET ...` fails to reset extension parameters that no longer exist Has attachments Nathan Bossart <nathandbossart@gmail.com>
2025-07-30T18:58:55Z Re: Postgres: Queries are too slow after upgrading to PG17 from PG15 Merlin Moncure <mmoncure@gmail.com>
2025-07-30T18:45:39Z Re: Postgres: Queries are too slow after upgrading to PG17 from PG15 Peter Geoghegan <pg@bowt.ie>
2025-07-30T18:34:43Z [PATCH v1 1/1] Allow ALTER SYSTEM to set unrecognized custom GUCs. Nathan Bossart <nathan@postgresql.org>
2025-07-30T18:34:43Z [PATCH v1 1/1] Allow ALTER SYSTEM to set unrecognized custom GUCs. Nathan Bossart <nathan@postgresql.org>
2025-07-30T10:54:04Z Re: BUG #18988: DROP SUBSCRIPTION locks not-yet-accessed database Has attachments vignesh C <vignesh21@gmail.com>
2025-07-30T03:27:35Z Re: BUG #19002: `pg_isready` unexpectedly succeeds on incorrect `--dbname` and/or `--username` Tom Lane <tgl@sss.pgh.pa.us>
2025-07-30T03:15:20Z Re: Unexpected Standby Shutdown on sync_replication_slots change shveta malik <shveta.malik@gmail.com>
2025-07-30T03:01:16Z Re: BUG #19002: `pg_isready` unexpectedly succeeds on incorrect `--dbname` and/or `--username` Samuel Marks <samuelmarks@gmail.com>
2025-07-29T23:33:45Z CREATE DATABASE copies datlocale even if datlocprovider differs Has attachments Jeff Davis <pgsql@j-davis.com>
2025-07-29T19:54:43Z Re: BUG #19002: `pg_isready` unexpectedly succeeds on incorrect `--dbname` and/or `--username` Jacob Champion <jacob.champion@enterprisedb.com>
2025-07-29T19:11:03Z BUG #19002: `pg_isready` unexpectedly succeeds on incorrect `--dbname` and/or `--username` PG Bug reporting form <noreply@postgresql.org>
2025-07-29T15:34:21Z Re: BUG #19001: PostgreSQL 17: CREATE MATERIALIZED VIEW fails with STABLE function using JSONB LATERAL joins Laurenz Albe <laurenz.albe@cybertec.at>
2025-07-29T15:31:59Z Re: BUG #19001: PostgreSQL 17: CREATE MATERIALIZED VIEW fails with STABLE function using JSONB LATERAL joins Tom Lane <tgl@sss.pgh.pa.us>
2025-07-29T13:55:07Z BUG #19001: PostgreSQL 17: CREATE MATERIALIZED VIEW fails with STABLE function using JSONB LATERAL joins PG Bug reporting form <noreply@postgresql.org>
2025-07-29T06:34:52Z Re: Unexpected Standby Shutdown on sync_replication_slots change Laurenz Albe <laurenz.albe@cybertec.at>