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-03-21T15:09:26Z Re: BUG #18859: ERROR: unexpected plan node type: 356 Richard Guo <guofenglinux@gmail.com>
2025-03-21T14:49:40Z Re: BUG #18859: ERROR: unexpected plan node type: 356 Has attachments Andrei Lepikhov <lepihov@gmail.com>
2025-03-21T13:00:53Z Re: BUG #18859: ERROR: unexpected plan node type: 356 Tom Lane <tgl@sss.pgh.pa.us>
2025-03-21T12:58:54Z Re: BUG #18859: ERROR: unexpected plan node type: 356 Andrei Lepikhov <lepihov@gmail.com>
2025-03-21T10:52:26Z BUG #18861: Not able to download rpm package PG Bug reporting form <noreply@postgresql.org>
2025-03-21T04:46:51Z BUG #18860: Test src/test/recovery/t/039_end_of_wal.pl is unstable PG Bug reporting form <noreply@postgresql.org>
2025-03-20T19:50:51Z Re: BUG #18854: PostgreSQL chooses a suboptimal execution plan when using a specific WHERE filter Andrei Lepikhov <lepihov@gmail.com>
2025-03-20T15:14:13Z PostgreSQL v15.12 fails to perform PG_UPGRADE from v13 and v9 on Windows Ben Caspi <benc@aidoc.com>
2025-03-20T15:00:58Z Re: BUG #18857: Abnormal string comparison results Bruce Momjian <bruce@momjian.us>
2025-03-20T14:56:20Z Re: BUG #18858: client does not support server version newer than 15.12 but actual version is 15.8.1 Tom Lane <tgl@sss.pgh.pa.us>
2025-03-20T14:46:15Z Re: BUG #18857: Abnormal string comparison results Tom Lane <tgl@sss.pgh.pa.us>
2025-03-20T13:53:59Z BUG #18859: ERROR: unexpected plan node type: 356 PG Bug reporting form <noreply@postgresql.org>
2025-03-20T12:34:11Z BUG #18858: client does not support server version newer than 15.12 but actual version is 15.8.1 PG Bug reporting form <noreply@postgresql.org>
2025-03-20T09:53:32Z BUG #18857: Abnormal string comparison results PG Bug reporting form <noreply@postgresql.org>
2025-03-20T03:19:43Z Re: BUG #18760: ../doc/src/sgml/postgres.sgml:24: element book: validity error : No declaration for attribute id of Tom Lane <tgl@sss.pgh.pa.us>
2025-03-20T01:44:43Z Re: 回复:Re: The != and +/- signs are joined together as an operator Tom Lane <tgl@sss.pgh.pa.us>
2025-03-20T01:32:58Z Re: BUG #18760: ../doc/src/sgml/postgres.sgml:24: element book: validity error : No declaration for attribute id of "David G. Johnston" <david.g.johnston@gmail.com>
2025-03-20T01:11:33Z 回复:Re: The != and +/- signs are joined together as an operator 谭忠涛 <zhongtao.tan@seaboxdata.com>
2025-03-19T19:53:50Z Re: BUG #18855: Using BRIN index with int8_bloom_ops produces incorrect results Tomas Vondra <tomas@vondra.me>
2025-03-19T17:11:07Z Re: BUG #18855: Using BRIN index with int8_bloom_ops produces incorrect results Has attachments Tomas Vondra <tomas@vondra.me>
2025-03-19T15:45:20Z Re: Possible bug acldefault function Tom Lane <tgl@sss.pgh.pa.us>
2025-03-19T14:34:39Z Re: The != and +/- signs are joined together as an operator Tom Lane <tgl@sss.pgh.pa.us>
2025-03-19T14:07:17Z Re: The != and +/- signs are joined together as an operator "David G. Johnston" <david.g.johnston@gmail.com>
2025-03-19T13:43:34Z Re: BUG #18855: Using BRIN index with int8_bloom_ops produces incorrect results Tomas Vondra <tomas@vondra.me>
2025-03-19T13:34:48Z Re: BUG #18854: PostgreSQL chooses a suboptimal execution plan when using a specific WHERE filter Yoni Sade <yonisade83@gmail.com>