Horton
Menu

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-04-08T12:38:17Z Error when using array_agg with filter where clause in pg16 and pg17 Kaimeh <kkaimeh@gmail.com>
2025-04-08T12:29:53Z Re: BUG #18883: Epoch issue "David G. Johnston" <david.g.johnston@gmail.com>
2025-04-08T12:00:14Z BUG #18883: Epoch issue PG Bug reporting form <noreply@postgresql.org>
2025-04-08T11:09:54Z Re: BUG #18882: Unexpected write skew at SERIALIZABLE with psycopg2.connect() Thomas Munro <thomas.munro@gmail.com>
2025-04-08T07:10:11Z BUG #18882: Unexpected write skew at SERIALIZABLE with psycopg2.connect() PG Bug reporting form <noreply@postgresql.org>
2025-04-08T06:56:25Z RE: BUG #18815: Logical replication worker Segmentation fault Has attachments "Zhijie Hou (Fujitsu)" <houzj.fnst@fujitsu.com>
2025-04-08T05:59:53Z Re: BUG #18815: Logical replication worker Segmentation fault Amit Kapila <amit.kapila16@gmail.com>
2025-04-08T05:50:56Z Re: PostgreSQL v15.12 fails to perform PG_UPGRADE from v13 and v9 on Windows Laurenz Albe <laurenz.albe@cybertec.at>
2025-04-07T16:22:45Z Re:   Re: Re: Revoke Connect Privilege from Database not working "David G. Johnston" <david.g.johnston@gmail.com>
2025-04-07T16:06:17Z Re:   Re: Re: Revoke Connect Privilege from Database not working Tom Lane <tgl@sss.pgh.pa.us>
2025-04-07T15:37:43Z Re:   Re: Re: Revoke Connect Privilege from Database not working "David G. Johnston" <david.g.johnston@gmail.com>
2025-04-07T14:59:36Z Re: PostgreSQL v15.12 fails to perform PG_UPGRADE from v13 and v9 on Windows Avi Uziel <avi.uziel@aidoc.com>
2025-04-07T14:27:41Z Aw:  Re: Re: Revoke Connect Privilege from Database not working "Ing. Marijo Kristo" <marijo.kristo@icloud.com>
2025-04-07T13:48:14Z Re: BUG #18880: Can't have a database without having postgres as a db_name and username Tom Lane <tgl@sss.pgh.pa.us>
2025-04-07T13:42:28Z Re: Re: Revoke Connect Privilege from Database not working "David G. Johnston" <david.g.johnston@gmail.com>
2025-04-07T09:58:39Z RE: BUG #18815: Logical replication worker Segmentation fault "Zhijie Hou (Fujitsu)" <houzj.fnst@fujitsu.com>
2025-04-07T09:37:08Z Re: BUG #18815: Logical replication worker Segmentation fault Amit Kapila <amit.kapila16@gmail.com>
2025-04-07T07:15:02Z Re: BUG #18880: Can't have a database without having postgres as a db_name and username "Daniel Westermann (DWE)" <daniel.westermann@dbi-services.com>
2025-04-06T18:16:13Z Re: BUG #18146: Rows reappearing in Tables after Auto-Vacuum Failure in PostgreSQL on Windows Noah Misch <noah@leadboat.com>
2025-04-06T02:20:27Z BUG #18880: Can't have a database without having postgres as a db_name and username PG Bug reporting form <noreply@postgresql.org>
2025-04-05T19:07:28Z Re: BUG #18878: PostgreSQL triggers Assertion Failure in Debug build Tom Lane <tgl@sss.pgh.pa.us>
2025-04-05T15:12:59Z Re: BUG #18877: PostgreSQL triggers assertion failure Tom Lane <tgl@sss.pgh.pa.us>
2025-04-05T15:00:44Z Re: BUG #18877: PostgreSQL triggers assertion failure Alvaro Herrera <alvherre@alvh.no-ip.org>
2025-04-05T14:47:28Z Re: BUG #18877: PostgreSQL triggers assertion failure Tom Lane <tgl@sss.pgh.pa.us>
2025-04-05T13:03:08Z Re: BUG #18877: PostgreSQL triggers assertion failure Has attachments Alvaro Herrera <alvherre@alvh.no-ip.org>