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-25T04:43:03Z BUG #18999: Equivalent queries processing WHERE IS NULL & WHERE IS NOT NULL produce mutually exclusive results PG Bug reporting form <noreply@postgresql.org>
2025-07-25T01:01:11Z Re: BUG #18996: Assertion fails in waiteventset.c when dropping database in single mode in PG18 Michael Paquier <michael@paquier.xyz>
2025-07-24T21:18:50Z Re: BUG #18998: No materialized views in INFORMATION_SCHEMA.TABLE_PRIVILEGES Tom Lane <tgl@sss.pgh.pa.us>
2025-07-24T21:06:57Z Re: BUG #18964: `ALTER DATABASE ... RESET ...` fails to reset extension parameters that no longer exist Laurenz Albe <laurenz.albe@cybertec.at>
2025-07-24T18:50:07Z Re: Unexpected Standby Shutdown on sync_replication_slots change Has attachments Fujii Masao <masao.fujii@gmail.com>
2025-07-24T17:50:36Z BUG #18998: No materialized views in INFORMATION_SCHEMA.TABLE_PRIVILEGES PG Bug reporting form <noreply@postgresql.org>
2025-07-24T17:49:54Z Re: BUG #18997: Two equivalent queries return different results Jinhui Lai <jinhui-lai@foxmail.com>
2025-07-24T17:33:36Z Re: BUG #18997: Two equivalent queries return different results Tom Lane <tgl@sss.pgh.pa.us>
2025-07-24T16:30:49Z Re: BUG #18964: `ALTER DATABASE ... RESET ...` fails to reset extension parameters that no longer exist Has attachments Nathan Bossart <nathandbossart@gmail.com>
2025-07-24T15:55:26Z Re: Unexpected Standby Shutdown on sync_replication_slots change Fujii Masao <masao.fujii@gmail.com>
2025-07-24T14:45:17Z BUG #18997: Two equivalent queries return different results PG Bug reporting form <noreply@postgresql.org>
2025-07-24T13:54:00Z Unexpected Standby Shutdown on sync_replication_slots change Hugo DUBOIS <hdubois@scaleway.com>
2025-07-24T13:46:12Z Re: BUG #18996: Assertion fails in waiteventset.c when dropping database in single mode in PG18 Has attachments Patrick Stählin <me@packi.ch>
2025-07-24T10:49:02Z Re: BUG #18897: Logical replication conflict after using pg_createsubscriber under heavy load Amit Kapila <amit.kapila16@gmail.com>
2025-07-24T10:28:05Z Re: BUG #18995: Building with GCC 14 fails: incompatible pointer struct pam_message Andrew Watkins <awatkins1966@gmail.com>
2025-07-24T09:49:47Z BUG #18996: Assertion fails in waiteventset.c when dropping database in single mode in PG18 PG Bug reporting form <noreply@postgresql.org>
2025-07-23T19:47:06Z Re: BUG #18995: Building with GCC 14 fails: incompatible pointer struct pam_message Tom Lane <tgl@sss.pgh.pa.us>
2025-07-23T18:41:02Z Re: BUG #18995: Building with GCC 14 fails: incompatible pointer struct pam_message Tom Lane <tgl@sss.pgh.pa.us>
2025-07-23T15:43:19Z Re: BUG #18995: Building with GCC 14 fails: incompatible pointer struct pam_message Tom Lane <tgl@sss.pgh.pa.us>
2025-07-23T15:31:10Z Re: BUG #18995: Building with GCC 14 fails: incompatible pointer struct pam_message Andrew Watkins <awatkins1966@gmail.com>
2025-07-23T14:44:06Z Re: BUG #18995: Building with GCC 14 fails: incompatible pointer struct pam_message Tom Lane <tgl@sss.pgh.pa.us>
2025-07-23T14:27:35Z Re: BUG #18995: Building with GCC 14 fails: incompatible pointer struct pam_message Tom Lane <tgl@sss.pgh.pa.us>
2025-07-23T13:25:49Z Re: BUG #18897: Logical replication conflict after using pg_createsubscriber under heavy load Has attachments Shlok Kyal <shlok.kyal.oss@gmail.com>
2025-07-23T10:00:55Z BUG #18995: Building with GCC 14 fails: incompatible pointer struct pam_message PG Bug reporting form <noreply@postgresql.org>
2025-07-23T09:27:04Z Re: Self referential foreign keys in partitioned table not working as expected Álvaro Herrera <alvherre@kurilemu.de>