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-15T13:42:30Z BUG #18933: PostgreSQL fails to handle JOIN operation involving Empty Table PG Bug reporting form <noreply@postgresql.org>
2025-05-15T13:12:06Z Re: Re: BUG #18927: Poor query plan - HashAggregate is more than twice as fast but at a higher cost 萧鸿骏 <23031212454@stu.xidian.edu.cn>
2025-05-15T13:06:35Z BUG #18932: PostgreSQL fails to handle EXCEPT operation when the left branch is an Empty Table PG Bug reporting form <noreply@postgresql.org>
2025-05-15T09:15:56Z Re: BUG #18927: Poor query plan - HashAggregate is more than twice as fast but at a higher cost Andrei Lepikhov <lepihov@gmail.com>
2025-05-15T08:45:03Z Re: BUG #18927: Poor query plan - HashAggregate is more than twice as fast but at a higher cost Dilip Kumar <dilipbalaut@gmail.com>
2025-05-15T07:40:40Z BUG #18931: Access to source rpms is not possible PG Bug reporting form <noreply@postgresql.org>
2025-05-15T07:26:12Z BUG #18930: PostgreSQL fails to handle INTERSECT operation involving Empty Table PG Bug reporting form <noreply@postgresql.org>
2025-05-15T05:33:28Z Postgres: Queries are too slow after upgrading to PG17 from PG15 Sajith Prabhakar Shetty <ssajith@blackduck.com>
2025-05-15T04:04:23Z BUG #18929: After the view is created, executed query against the view definition, reported syntax error. PG Bug reporting form <noreply@postgresql.org>
2025-05-15T00:57:21Z RE: pg16 ALTER ROLE [NO]INHERIT has no effect on existing grants Jason Matthew <Jason.Matthew@sas.com>
2025-05-14T21:57:45Z information_schema query not working in PostgreSQL version 17 Has attachments Jorge Campins <jrcampins@gmail.com>
2025-05-14T21:16:59Z Re: pg16 ALTER ROLE [NO]INHERIT has no effect on existing grants "David G. Johnston" <david.g.johnston@gmail.com>
2025-05-14T20:27:29Z pg16 ALTER ROLE [NO]INHERIT has no effect on existing grants Jason Matthew <Jason.Matthew@sas.com>
2025-05-14T19:35:08Z Re: BUG #18925: Heap-buffer-overflow: pglz_compress with pglz_stategy_always Daniel Gustafsson <daniel@yesql.se>
2025-05-14T16:38:22Z Re: BUG #18928: postgres_fdw search_path not reset causing pgbouncer pool_mode=transaction using the wrong schema Jackie Li <jackie.space@gmail.com>
2025-05-14T16:30:50Z Re: BUG #18928: postgres_fdw search_path not reset causing pgbouncer pool_mode=transaction using the wrong schema Jackie Li <jackie.space@gmail.com>
2025-05-14T15:30:12Z Re: BUG #18928: postgres_fdw search_path not reset causing pgbouncer pool_mode=transaction using the wrong schema Tom Lane <tgl@sss.pgh.pa.us>
2025-05-14T15:06:35Z Re: BUG #18928: postgres_fdw search_path not reset causing pgbouncer pool_mode=transaction using the wrong schema Has attachments Matheus Alcantara <matheusssilv97@gmail.com>
2025-05-14T12:57:16Z Re: BUG #18926: PostgreSQL 17.5 produces malformed binary COPY output (`GPOCYP` instead of `PGCOPY`) across platform Tom Lane <tgl@sss.pgh.pa.us>
2025-05-14T12:37:36Z BUG #18928: postgres_fdw search_path not reset causing pgbouncer pool_mode=transaction using the wrong schema PG Bug reporting form <noreply@postgresql.org>
2025-05-14T11:10:08Z 回复: pg_restore error with partitioned table having exclude constraint Has attachments Li Japin <japinli@hotmail.com>
2025-05-14T10:40:14Z Re: Unexpected output of PgRules Manav Kumar <mkumar@yugabyte.com>
2025-05-14T09:14:30Z Unexpected output of PgRules Manav Kumar <mkumar@yugabyte.com>
2025-05-14T08:23:19Z Re: BUG #18927: Poor query plan - HashAggregate is more than twice as fast but at a higher cost 萧鸿骏 <23031212454@stu.xidian.edu.cn>
2025-05-14T08:18:45Z BUG #18927: Poor query plan - HashAggregate is more than twice as fast but at a higher cost PG Bug reporting form <noreply@postgresql.org>