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-23T09:24:49Z Re: BUG #18897: Logical replication conflict after using pg_createsubscriber under heavy load vignesh C <vignesh21@gmail.com>
2025-07-23T09:19:42Z Re: BUG #18897: Logical replication conflict after using pg_createsubscriber under heavy load Amit Kapila <amit.kapila16@gmail.com>
2025-07-23T04:35:01Z Re: BUG #18897: Logical replication conflict after using pg_createsubscriber under heavy load Shlok Kyal <shlok.kyal.oss@gmail.com>
2025-07-23T03:50:02Z Re: BUG #18992: Autovacuum triggering assert - LWLockAnyHeldByMe Dilip Kumar <dilipbalaut@gmail.com>
2025-07-23T01:39:30Z Re: BUG #18992: Autovacuum triggering assert - LWLockAnyHeldByMe Michael Paquier <michael@paquier.xyz>
2025-07-23T00:08:55Z Re: [PERFORMANCE] regression: EXECUTE loop TRUNCATE slower in 17.5 vs 17.2 Tom Lane <tgl@sss.pgh.pa.us>
2025-07-22T23:23:25Z [PERFORMANCE] regression: EXECUTE loop TRUNCATE slower in 17.5 vs 17.2 Guilherme Luis França <gulybyte@gmail.com>
2025-07-22T12:21:33Z RE: BUG #18897: Logical replication conflict after using pg_createsubscriber under heavy load "Hayato Kuroda (Fujitsu)" <kuroda.hayato@fujitsu.com>
2025-07-22T11:24:29Z Re: BUG #18897: Logical replication conflict after using pg_createsubscriber under heavy load Has attachments Shlok Kyal <shlok.kyal.oss@gmail.com>
2025-07-22T02:27:24Z Re: BUG #18964: `ALTER DATABASE ... RESET ...` fails to reset extension parameters that no longer exist Laurenz Albe <laurenz.albe@cybertec.at>
2025-07-21T14:38:26Z Re: BUG #18993: [BUG] Unreachable code in pg_next_dst_boundary() Tom Lane <tgl@sss.pgh.pa.us>
2025-07-21T14:29:32Z Re: BUG #18993: [BUG] Unreachable code in pg_next_dst_boundary() Nathan Bossart <nathandbossart@gmail.com>
2025-07-21T12:29:16Z BUG #18993: [BUG] Unreachable code in pg_next_dst_boundary() PG Bug reporting form <noreply@postgresql.org>
2025-07-21T07:21:14Z Re: BUG #18992: Autovacuum triggering assert - LWLockAnyHeldByMe Rahila Syed <rahilasyed90@gmail.com>
2025-07-21T05:52:18Z Re: BUG #18992: Autovacuum triggering assert - LWLockAnyHeldByMe Dilip Kumar <dilipbalaut@gmail.com>
2025-07-20T14:31:02Z BUG #18992: Autovacuum triggering assert - LWLockAnyHeldByMe PG Bug reporting form <noreply@postgresql.org>
2025-07-19T09:43:49Z BUG #18991: NUMA test fails on machine with two NUMA nodes when building 18beta2 PG Bug reporting form <noreply@postgresql.org>
2025-07-18T10:36:41Z Re: BUG #18986: SIGSEGV in nodeModifyTable.c during Parallel Execution Yaroslav Syrytsia <me@ys.lc>
2025-07-18T09:19:14Z Re: BUG #18986: SIGSEGV in nodeModifyTable.c during Parallel Execution Dean Rasheed <dean.a.rasheed@gmail.com>
2025-07-17T15:55:18Z Re: Postgres: Queries are too slow after upgrading to PG17 from PG15 Peter Geoghegan <pg@bowt.ie>
2025-07-17T15:49:39Z Re: Postgres: Queries are too slow after upgrading to PG17 from PG15 Sajith Prabhakar Shetty <ssajith@blackduck.com>
2025-07-17T15:48:27Z Re: BUG #18984: Empty prepared statement from psql \parse triggers assert in PortalRunMulti Álvaro Herrera <alvherre@kurilemu.de>
2025-07-17T15:05:01Z Re: Postgres: Queries are too slow after upgrading to PG17 from PG15 Peter Geoghegan <pg@bowt.ie>
2025-07-17T15:00:56Z Re: BUG #18984: Empty prepared statement from psql \parse triggers assert in PortalRunMulti Tom Lane <tgl@sss.pgh.pa.us>
2025-07-17T13:58:44Z Re: BUG #18989: Output of \sf does not match original source for E quoted strings (unlike \df+ used to) Tom Lane <tgl@sss.pgh.pa.us>