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-12-23T07:49:41Z Re: BUG #19360: Bug Report: Logical Replication initial sync fails with "conflict=update_origin_differs" PG12 toPG18 Rahila Syed <rahilasyed90@gmail.com>
2025-12-22T22:37:18Z Re: BUG #19355: Attempt to insert data unexpectedly during concurrent update Dean Rasheed <dean.a.rasheed@gmail.com>
2025-12-22T14:51:02Z Re: BUG #19355: Attempt to insert data unexpectedly during concurrent update Bh W <wangbihua.cn@gmail.com>
2025-12-22T08:55:15Z BUG #19360: Bug Report: Logical Replication initial sync fails with "conflict=update_origin_differs" PG12 toPG18 PG Bug reporting form <noreply@postgresql.org>
2025-12-19T23:12:34Z Re: BUG #19359: Row level security: Upserts require insert policies in the update path Dean Rasheed <dean.a.rasheed@gmail.com>
2025-12-19T17:40:43Z Re: BUG #19359: Row level security: Upserts require insert policies in the update path Srinath Reddy Sadipiralla <srinath2133@gmail.com>
2025-12-18T15:03:28Z BUG #19359: Row level security: Upserts require insert policies in the update path PG Bug reporting form <noreply@postgresql.org>
2025-12-18T13:30:51Z Re: [BUG] PostgreSQL 14.5: Data corruption in table tb_workstation_message (possible fstrim-related on eMMC) Greg Sabino Mullane <htamfids@gmail.com>
2025-12-18T08:56:08Z Re: GROUP BY ROLLUP queries on views trigger full table scans (index usage not optimized) Richard Guo <guofenglinux@gmail.com>
2025-12-18T08:40:56Z Re: [BUG] PostgreSQL 14.5: Data corruption in table tb_workstation_message (possible fstrim-related on eMMC) Laurenz Albe <laurenz.albe@cybertec.at>
2025-12-18T06:42:56Z [BUG] PostgreSQL 14.5: Data corruption in table tb_workstation_message (possible fstrim-related on eMMC) 第108次明天 <87326549@qq.com>
2025-12-17T21:37:24Z Re: BUG #19358: Short circuit optimization exists in generic plan but missed in custom plan Tom Lane <tgl@sss.pgh.pa.us>
2025-12-17T17:11:07Z Re: BUG #19357: PostgreSQL generates a custom plan that performsworsethan the generic plan for a certain query. Greg Sabino Mullane <htamfids@gmail.com>
2025-12-17T16:33:16Z Re: BUG #19357: PostgreSQL generates a custom plan thatperformsworsethan the generic plan for a certain query. Pavel Stehule <pavel.stehule@gmail.com>
2025-12-17T16:20:08Z Re: BUG #19357: PostgreSQL generates a custom plan thatperformsworsethan the generic plan for a certain query. ZhangChi <798604270@qq.com>
2025-12-17T16:15:21Z Re: BUG #19357: PostgreSQL generates a custom plan that performsworsethan the generic plan for a certain query. Pavel Stehule <pavel.stehule@gmail.com>
2025-12-17T16:08:49Z Re: BUG #19357: PostgreSQL generates a custom plan that performsworsethan the generic plan for a certain query. ZhangChi <798604270@qq.com>
2025-12-17T15:53:00Z Re: BUG #19357: PostgreSQL generates a custom plan that performsworse than the generic plan for a certain query. Pavel Stehule <pavel.stehule@gmail.com>
2025-12-17T15:52:23Z Re: BUG #19357: PostgreSQL generates a custom plan that performs worse than the generic plan for a certain query. ZhangChi <798604270@qq.com>
2025-12-17T15:44:03Z Re: BUG #19350: Short circuit optimization missed when runningsqlscriptes in JDBC Tom Lane <tgl@sss.pgh.pa.us>
2025-12-17T15:39:21Z Re: BUG #19350: Short circuit optimization missed when runningsqlscriptes in JDBC Dave Cramer <davecramer@postgres.rocks>
2025-12-17T15:39:10Z Re: BUG #19357: PostgreSQL generates a custom plan that performs worse than the generic plan for a certain query. Tom Lane <tgl@sss.pgh.pa.us>
2025-12-17T15:33:25Z Re: BUG #19350: Short circuit optimization missed when runningsqlscriptes in JDBC Dave Cramer <davecramer@postgres.rocks>
2025-12-17T15:17:30Z Re: BUG #19357: PostgreSQL generates a custom plan that performsworse than the generic plan for a certain query. ZhangChi <798604270@qq.com>
2025-12-17T15:14:11Z Re: Possible performance issues: DISTINCT ON + ORDER BY and JIT with aggregation Laurenz Albe <laurenz.albe@cybertec.at>