pg.ddx.io pgsql-hackers@postgresql.org mailing list archive
help / color / mirror / Atom feedSevere performance degradation with concurrent updates due to excessive EvalPlanQual (EPQ) re‑evaluation
2026-09-15 08:05 UTC Wei Sun <936739278@qq.com>
` Re: Severe performance degradation with concurrent updates due to excessive EvalPlanQual (EPQ) re‑evaluation
2026-09-15 09:15 UTC Osama Abdul Qader <osamaabdulqader.cs@gmail.com>
` Re: Severe performance degradation with concurrent updates due to excessive EvalPlanQual (EPQ) re‑evaluation
2026-09-15 10:49 UTC Osama Abdul Qader <osamaabdulqader.cs@gmail.com>
` Re: Severe performance degradation with concurrent updates due to excessive EvalPlanQual (EPQ) re‑evaluation
2026-09-15 12:59 UTC Wei Sun <936739278@qq.com>
` Re: Severe performance degradation with concurrent updates due to excessive EvalPlanQual (EPQ) re‑evaluation
2026-09-16 07:27 UTC Osama Abdul Qader <osamaabdulqader.cs@gmail.com>
` Re: Severe performance degradation with concurrent updates due to excessive EvalPlanQual (EPQ) re‑evaluation
2026-09-18 12:58 UTC Osama Abdul Qader <osamaabdulqader.cs@gmail.com>
` Re: Severe performance degradation with concurrent updates due to excessive EvalPlanQual (EPQ) re‑evaluation
2026-09-20 02:50 UTC Wei Sun <936739278@qq.com>
` Re: Severe performance degradation with concurrent updates due to excessive EvalPlanQual (EPQ) re‑evaluation
2026-09-21 15:25 UTC Osama Abdul Qader <osamaabdulqader.cs@gmail.com>
` Re: Severe performance degradation with concurrent updates due to excessive EvalPlanQual (EPQ) re‑evaluation
2026-09-21 18:58 UTC Andres Freund <andres@anarazel.de>
` Re: Severe performance degradation with concurrent updates due to excessive EvalPlanQual (EPQ) re‑evaluation
2026-09-22 02:15 UTC Wei Sun <936739278@qq.com>
` Re: Severe performance degradation with concurrent updates due to excessive EvalPlanQual (EPQ) re‑evaluation
2026-09-25 01:23 UTC Osama Abdul Qader <osamaabdulqader.cs@gmail.com>
` Re: Severe performance degradation with concurrent updates due to excessive EvalPlanQual (EPQ) re‑evaluation
2026-09-25 03:05 UTC Osama Abdul Qader <osamaabdulqader.cs@gmail.com>
` Re: Severe performance degradation with concurrent updates due to excessive EvalPlanQual (EPQ) re‑evaluation
2026-09-25 08:37 UTC Wei Sun <936739278@qq.com>
` Re: Severe performance degradation with concurrent updates due to excessive EvalPlanQual (EPQ) re‑evaluation
2026-09-25 14:05 UTC Osama Abdul Qader <osamaabdulqader.cs@gmail.com>
` Re: Severe performance degradation with concurrent updates due to excessive EvalPlanQual (EPQ) re‑evaluation
2026-10-02 20:34 UTC Osama Abdul Qader <osamaabdulqader.cs@gmail.com>
[15+ messages in thread]
Fix GROUP BY ALL handling of ORDER BY operator semantics
2026-06-29 07:20 UTC Chao Li <li.evan.chao@gmail.com>
` Re: Fix GROUP BY ALL handling of ORDER BY operator semantics
2026-06-29 09:09 UTC Chao Li <li.evan.chao@gmail.com>
` Re: Fix GROUP BY ALL handling of ORDER BY operator semantics
2026-07-07 20:00 UTC Miłosz Bieniek <bieniek.milosz@proton.me>
` Re: Fix GROUP BY ALL handling of ORDER BY operator semantics
2026-07-13 20:10 UTC Daniel Gustafsson <daniel@yesql.se>
` Re: Fix GROUP BY ALL handling of ORDER BY operator semantics
2026-07-14 00:44 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: Fix GROUP BY ALL handling of ORDER BY operator semantics
2026-07-14 14:01 UTC Daniel Gustafsson <daniel@yesql.se>
` Re: Fix GROUP BY ALL handling of ORDER BY operator semantics
2026-07-14 16:08 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: Fix GROUP BY ALL handling of ORDER BY operator semantics
2026-07-14 16:33 UTC Chao Li <li.evan.chao@gmail.com>
` Re: Fix GROUP BY ALL handling of ORDER BY operator semantics
2026-07-15 08:01 UTC Daniel Gustafsson <daniel@yesql.se>
` Re: Fix GROUP BY ALL handling of ORDER BY operator semantics
2026-07-15 14:53 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: Fix GROUP BY ALL handling of ORDER BY operator semantics
2026-07-17 20:15 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: Fix GROUP BY ALL handling of ORDER BY operator semantics
2026-07-17 21:59 UTC Chao Li <li.evan.chao@gmail.com>
` Re: Fix GROUP BY ALL handling of ORDER BY operator semantics
2026-08-20 02:12 UTC Bruce Momjian <bruce@momjian.us>
` Re: Fix GROUP BY ALL handling of ORDER BY operator semantics
2026-10-02 14:55 UTC David Christensen <david+pg@pgguru.net>
[14+ messages in thread]
Report oldest xmin source when autovacuum cannot remove tuples
2025-10-31 06:31 UTC Shinya Kato <shinya11.kato@gmail.com>
` Re: Report oldest xmin source when autovacuum cannot remove tuples
2025-10-31 08:00 UTC wenhui qiu <qiuwenhuifx@gmail.com>
` Re: Report oldest xmin source when autovacuum cannot remove tuples
2025-11-04 01:29 UTC Shinya Kato <shinya11.kato@gmail.com>
` Re: Report oldest xmin source when autovacuum cannot remove tuples
2025-11-04 15:58 UTC Fujii Masao <masao.fujii@gmail.com>
` Re: Report oldest xmin source when autovacuum cannot remove tuples
2025-11-11 10:40 UTC wenhui qiu <qiuwenhuifx@gmail.com>
` Re: Report oldest xmin source when autovacuum cannot remove tuples
2025-11-15 00:25 UTC Sami Imseih <samimseih@gmail.com>
` Re: Report oldest xmin source when autovacuum cannot remove tuples
2025-11-17 01:43 UTC wenhui qiu <qiuwenhuifx@gmail.com>
` Re: Report oldest xmin source when autovacuum cannot remove tuples
2025-11-17 02:51 UTC Dilip Kumar <dilipbalaut@gmail.com>
` Re: Report oldest xmin source when autovacuum cannot remove tuples
2025-11-17 18:35 UTC Sami Imseih <samimseih@gmail.com>
` Re: Report oldest xmin source when autovacuum cannot remove tuples
2025-12-18 00:30 UTC Andres Freund <andres@anarazel.de>
` Re: Report oldest xmin source when autovacuum cannot remove tuples
2025-12-26 05:34 UTC Shinya Kato <shinya11.kato@gmail.com>
` Re: Report oldest xmin source when autovacuum cannot remove tuples
2026-01-05 22:02 UTC Sami Imseih <samimseih@gmail.com>
` Re: Report oldest xmin source when autovacuum cannot remove tuples
2026-01-22 06:58 UTC wenhui qiu <qiuwenhuifx@gmail.com>
` Re: Report oldest xmin source when autovacuum cannot remove tuples
2026-02-05 04:39 UTC Shinya Kato <shinya11.kato@gmail.com>
` Re: Report oldest xmin source when autovacuum cannot remove tuples
2026-03-16 07:59 UTC wenhui qiu <qiuwenhuifx@gmail.com>
` Re: Report oldest xmin source when autovacuum cannot remove tuples
2026-03-16 11:19 UTC Japin Li <japinli@hotmail.com>
` Re: Report oldest xmin source when autovacuum cannot remove tuples
2026-05-22 13:05 UTC Shinya Kato <shinya11.kato@gmail.com>
` Re: Report oldest xmin source when autovacuum cannot remove tuples
2026-05-23 01:40 UTC Japin Li <japinli@hotmail.com>
` Re: Report oldest xmin source when autovacuum cannot remove tuples
2026-05-23 05:22 UTC Shinya Kato <shinya11.kato@gmail.com>
` Re: Report oldest xmin source when autovacuum cannot remove tuples
2026-05-23 06:00 UTC Shinya Kato <shinya11.kato@gmail.com>
` Re: Report oldest xmin source when autovacuum cannot remove tuples
2026-05-23 10:17 UTC wenhui qiu <qiuwenhuifx@gmail.com>
` Re: Report oldest xmin source when autovacuum cannot remove tuples
2026-05-23 13:35 UTC Laurenz Albe <laurenz.albe@cybertec.at>
` Re: Report oldest xmin source when autovacuum cannot remove tuples
2026-05-28 05:34 UTC Shinya Kato <shinya11.kato@gmail.com>
` Re: Report oldest xmin source when autovacuum cannot remove tuples
2026-05-30 02:31 UTC Scott Ray <scott@scottray.io>
` Re: Report oldest xmin source when autovacuum cannot remove tuples
2026-05-31 13:06 UTC Shinya Kato <shinya11.kato@gmail.com>
` Re: Report oldest xmin source when autovacuum cannot remove tuples
2026-06-02 07:57 UTC Kyotaro Horiguchi <horikyota.ntt@gmail.com>
` Re: Report oldest xmin source when autovacuum cannot remove tuples
2026-06-02 23:34 UTC Sami Imseih <samimseih@gmail.com>
` Re: Report oldest xmin source when autovacuum cannot remove tuples
2026-06-03 01:05 UTC Scott Ray <scott@scottray.io>
` Re: Report oldest xmin source when autovacuum cannot remove tuples
2026-06-03 01:11 UTC Shinya Kato <shinya11.kato@gmail.com>
` Re: Report oldest xmin source when autovacuum cannot remove tuples
2026-06-03 01:24 UTC Shinya Kato <shinya11.kato@gmail.com>
` Re: Report oldest xmin source when autovacuum cannot remove tuples
2026-06-03 02:32 UTC wenhui qiu <qiuwenhuifx@gmail.com>
` Re: Report oldest xmin source when autovacuum cannot remove tuples
2026-06-03 05:58 UTC Japin Li <japinli@hotmail.com>
` Re: Report oldest xmin source when autovacuum cannot remove tuples
2026-06-03 17:36 UTC Jacob Champion <jacob.champion@enterprisedb.com>
` Re: Report oldest xmin source when autovacuum cannot remove tuples
2026-06-06 18:40 UTC Scott Ray <scott@scottray.io>
` Re: Report oldest xmin source when autovacuum cannot remove tuples
2026-06-08 16:35 UTC Sami Imseih <samimseih@gmail.com>
` Re: Report oldest xmin source when autovacuum cannot remove tuples
2026-06-26 09:07 UTC Shinya Kato <shinya11.kato@gmail.com>
` Re: Report oldest xmin source when autovacuum cannot remove tuples
2026-06-26 14:54 UTC wenhui qiu <qiuwenhuifx@gmail.com>
` Re: Report oldest xmin source when autovacuum cannot remove tuples
2026-06-27 08:08 UTC Shinya Kato <shinya11.kato@gmail.com>
` Re: Report oldest xmin source when autovacuum cannot remove tuples
2026-06-29 08:22 UTC Kyotaro Horiguchi <horikyota.ntt@gmail.com>
` Re: Report oldest xmin source when autovacuum cannot remove tuples
2026-06-29 15:22 UTC Bharath Rupireddy <bharath.rupireddyforpostgres@gmail.com>
` Re: Report oldest xmin source when autovacuum cannot remove tuples
2026-06-29 15:31 UTC Sami Imseih <samimseih@gmail.com>
` Re: Report oldest xmin source when autovacuum cannot remove tuples
2026-07-07 15:44 UTC Shinya Kato <shinya11.kato@gmail.com>
` Re: Report oldest xmin source when autovacuum cannot remove tuples
2026-07-07 16:16 UTC Shinya Kato <shinya11.kato@gmail.com>
` Re: Report oldest xmin source when autovacuum cannot remove tuples
2026-07-07 16:34 UTC Shinya Kato <shinya11.kato@gmail.com>
` Re: Report oldest xmin source when autovacuum cannot remove tuples
2026-07-12 00:52 UTC Scott Ray <scott@scottray.io>
` Re: Report oldest xmin source when autovacuum cannot remove tuples
2026-07-13 15:06 UTC Jacob Champion <jacob.champion@enterprisedb.com>
` Re: Report oldest xmin source when autovacuum cannot remove tuples
2026-07-14 19:38 UTC Bharath Rupireddy <bharath.rupireddyforpostgres@gmail.com>
` Re: Report oldest xmin source when autovacuum cannot remove tuples
2026-07-14 22:13 UTC Sami Imseih <samimseih@gmail.com>
` Re: Report oldest xmin source when autovacuum cannot remove tuples
2026-07-15 03:47 UTC wenhui qiu <qiuwenhuifx@gmail.com>
` Re: Report oldest xmin source when autovacuum cannot remove tuples
2026-07-17 18:11 UTC Scott Ray <scott@scottray.io>
` Re: Report oldest xmin source when autovacuum cannot remove tuples
2026-08-05 13:22 UTC Shinya Kato <shinya11.kato@gmail.com>
` Re: Report oldest xmin source when autovacuum cannot remove tuples
2026-08-08 01:58 UTC Scott Ray <scott@scottray.io>
` Re: Report oldest xmin source when autovacuum cannot remove tuples
2026-10-01 12:20 UTC Shinya Kato <shinya11.kato@gmail.com>
` Re: Report oldest xmin source when autovacuum cannot remove tuples
2026-10-02 06:19 UTC wenhui qiu <qiuwenhuifx@gmail.com>
` Re: Report oldest xmin source when autovacuum cannot remove tuples
2026-10-02 07:48 UTC Shinya Kato <shinya11.kato@gmail.com>
[55+ messages in thread]
pg_dump: assert failure sorting casts/transforms
2026-08-20 10:20 UTC Alexander Kukushkin <cyberdemn@gmail.com>
` Re: pg_dump: assert failure sorting casts/transforms
2026-08-20 11:03 UTC Nitin Jadhav <nitinjadhavpostgres@gmail.com>
` Re: pg_dump: assert failure sorting casts/transforms
2026-08-20 11:40 UTC Alexander Kukushkin <cyberdemn@gmail.com>
` Re: pg_dump: assert failure sorting casts/transforms
2026-08-21 07:40 UTC Nitin Jadhav <nitinjadhavpostgres@gmail.com>
` Re: pg_dump: assert failure sorting casts/transforms
2026-08-21 09:59 UTC Alexander Kukushkin <cyberdemn@gmail.com>
` Re: pg_dump: assert failure sorting casts/transforms
2026-08-22 13:59 UTC Nitin Jadhav <nitinjadhavpostgres@gmail.com>
` Re: pg_dump: assert failure sorting casts/transforms
2026-09-09 00:03 UTC Noah Misch <noah@leadboat.com>
` Re: pg_dump: assert failure sorting casts/transforms
2026-10-02 07:25 UTC Alexander Kukushkin <cyberdemn@gmail.com>
[8+ messages in thread]
wiki upgrade
2026-10-02 06:58 UTC Álvaro Herrera <alvherre@kurilemu.de>
` Re: wiki upgrade
2026-10-02 07:21 UTC Álvaro Herrera <alvherre@kurilemu.de>
[2+ messages in thread]
pg_dump: ALTER INDEX SET STATISTICS missing for index-backed constraints
2026-07-14 12:45 UTC Zsolt Parragi <zsolt.parragi@percona.com>
` Re: pg_dump: ALTER INDEX SET STATISTICS missing for index-backed constraints
2026-09-28 20:56 UTC Andrew Krylosov <krylosov.andrew@gmail.com>
` Re: pg_dump: ALTER INDEX SET STATISTICS missing for index-backed constraints
2026-09-29 07:39 UTC Chao Li <li.evan.chao@gmail.com>
` Re: pg_dump: ALTER INDEX SET STATISTICS missing for index-backed constraints
2026-10-01 11:50 UTC Zsolt Parragi <zsolt.parragi@percona.com>
` Re: pg_dump: ALTER INDEX SET STATISTICS missing for index-backed constraints
2026-10-02 05:48 UTC Michael Paquier <michael@paquier.xyz>
[5+ messages in thread]
Commitfest PG20-2 is now closed
2026-10-01 02:56 UTC shihao zhong <zhong950419@gmail.com>
` Re: Commitfest PG20-2 is now closed
2026-10-01 08:27 UTC Álvaro Herrera <alvherre@kurilemu.de>
` Re: Commitfest PG20-2 is now closed
2026-10-01 15:00 UTC Jacob Champion <jacob.champion@enterprisedb.com>
` Re: Commitfest PG20-2 is now closed
2026-10-01 19:48 UTC Jelte Fennema-Nio <postgres@jeltef.nl>
` Re: Commitfest PG20-2 is now closed
2026-10-02 04:09 UTC shihao zhong <zhong950419@gmail.com>
[5+ messages in thread]
[PATCH] Add pg_get_table_ddl() to reconstruct CREATE TABLE statements
2026-06-03 12:58 UTC Akshay Joshi <akshay.joshi@enterprisedb.com>
` Re: [PATCH] Add pg_get_table_ddl() to reconstruct CREATE TABLE statements
2026-06-08 11:30 UTC Akshay Joshi <akshay.joshi@enterprisedb.com>
` Re: [PATCH] Add pg_get_table_ddl() to reconstruct CREATE TABLE statements
2026-06-08 19:11 UTC Marcos Pegoraro <marcos@f10.com.br>
` Re: [PATCH] Add pg_get_table_ddl() to reconstruct CREATE TABLE statements
2026-06-08 21:12 UTC Zsolt Parragi <zsolt.parragi@percona.com>
` Re: [PATCH] Add pg_get_table_ddl() to reconstruct CREATE TABLE statements
2026-06-09 08:58 UTC Akshay Joshi <akshay.joshi@enterprisedb.com>
` Re: [PATCH] Add pg_get_table_ddl() to reconstruct CREATE TABLE statements
2026-06-09 19:17 UTC Zsolt Parragi <zsolt.parragi@percona.com>
` Re: [PATCH] Add pg_get_table_ddl() to reconstruct CREATE TABLE statements
2026-06-10 11:24 UTC Akshay Joshi <akshay.joshi@enterprisedb.com>
` Re: [PATCH] Add pg_get_table_ddl() to reconstruct CREATE TABLE statements
2026-06-10 20:43 UTC Zsolt Parragi <zsolt.parragi@percona.com>
` Re: [PATCH] Add pg_get_table_ddl() to reconstruct CREATE TABLE statements
2026-06-11 07:48 UTC Akshay Joshi <akshay.joshi@enterprisedb.com>
` Re: [PATCH] Add pg_get_table_ddl() to reconstruct CREATE TABLE statements
2026-06-11 13:07 UTC Marcos Pegoraro <marcos@f10.com.br>
` Re: [PATCH] Add pg_get_table_ddl() to reconstruct CREATE TABLE statements
2026-06-11 21:00 UTC Zsolt Parragi <zsolt.parragi@percona.com>
` Re: [PATCH] Add pg_get_table_ddl() to reconstruct CREATE TABLE statements
2026-06-12 01:10 UTC Kyotaro Horiguchi <horikyota.ntt@gmail.com>
` Re: [PATCH] Add pg_get_table_ddl() to reconstruct CREATE TABLE statements
2026-06-15 07:52 UTC Akshay Joshi <akshay.joshi@enterprisedb.com>
` Re: [PATCH] Add pg_get_table_ddl() to reconstruct CREATE TABLE statements
2026-06-15 08:55 UTC Akshay Joshi <akshay.joshi@enterprisedb.com>
` Re: [PATCH] Add pg_get_table_ddl() to reconstruct CREATE TABLE statements
2026-06-15 21:04 UTC Marcos Pegoraro <marcos@f10.com.br>
` Re: [PATCH] Add pg_get_table_ddl() to reconstruct CREATE TABLE statements
2026-06-19 12:19 UTC Akshay Joshi <akshay.joshi@enterprisedb.com>
` Re: [PATCH] Add pg_get_table_ddl() to reconstruct CREATE TABLE statements
2026-06-19 19:45 UTC Zsolt Parragi <zsolt.parragi@percona.com>
` Re: [PATCH] Add pg_get_table_ddl() to reconstruct CREATE TABLE statements
2026-06-22 06:26 UTC Akshay Joshi <akshay.joshi@enterprisedb.com>
` Re: [PATCH] Add pg_get_table_ddl() to reconstruct CREATE TABLE statements
2026-06-22 06:54 UTC Chao Li <li.evan.chao@gmail.com>
` Re: [PATCH] Add pg_get_table_ddl() to reconstruct CREATE TABLE statements
2026-06-22 12:40 UTC Akshay Joshi <akshay.joshi@enterprisedb.com>
` Re: [PATCH] Add pg_get_table_ddl() to reconstruct CREATE TABLE statements
2026-06-22 14:00 UTC Chao Li <li.evan.chao@gmail.com>
` Re: [PATCH] Add pg_get_table_ddl() to reconstruct CREATE TABLE statements
2026-06-22 14:11 UTC Akshay Joshi <akshay.joshi@enterprisedb.com>
` Re: [PATCH] Add pg_get_table_ddl() to reconstruct CREATE TABLE statements
2026-06-22 14:54 UTC Marcos Pegoraro <marcos@f10.com.br>
` Re: [PATCH] Add pg_get_table_ddl() to reconstruct CREATE TABLE statements
2026-06-22 18:56 UTC Zsolt Parragi <zsolt.parragi@percona.com>
` Re: [PATCH] Add pg_get_table_ddl() to reconstruct CREATE TABLE statements
2026-06-23 02:18 UTC Chao Li <li.evan.chao@gmail.com>
` Re: [PATCH] Add pg_get_table_ddl() to reconstruct CREATE TABLE statements
2026-06-23 06:15 UTC Kyotaro Horiguchi <horikyota.ntt@gmail.com>
` Re: [PATCH] Add pg_get_table_ddl() to reconstruct CREATE TABLE statements
2026-06-23 07:21 UTC Kyotaro Horiguchi <horikyota.ntt@gmail.com>
` Re: [PATCH] Add pg_get_table_ddl() to reconstruct CREATE TABLE statements
2026-06-23 08:57 UTC Akshay Joshi <akshay.joshi@enterprisedb.com>
` Re: [PATCH] Add pg_get_table_ddl() to reconstruct CREATE TABLE statements
2026-06-23 09:22 UTC Akshay Joshi <akshay.joshi@enterprisedb.com>
` Re: [PATCH] Add pg_get_table_ddl() to reconstruct CREATE TABLE statements
2026-06-23 13:34 UTC Akshay Joshi <akshay.joshi@enterprisedb.com>
` Re: [PATCH] Add pg_get_table_ddl() to reconstruct CREATE TABLE statements
2026-06-23 14:03 UTC Marcos Pegoraro <marcos@f10.com.br>
` Re: [PATCH] Add pg_get_table_ddl() to reconstruct CREATE TABLE statements
2026-06-23 20:05 UTC Zsolt Parragi <zsolt.parragi@percona.com>
` Re: [PATCH] Add pg_get_table_ddl() to reconstruct CREATE TABLE statements
2026-06-24 08:23 UTC Akshay Joshi <akshay.joshi@enterprisedb.com>
` Re: [PATCH] Add pg_get_table_ddl() to reconstruct CREATE TABLE statements
2026-06-24 09:16 UTC Akshay Joshi <akshay.joshi@enterprisedb.com>
` Re: [PATCH] Add pg_get_table_ddl() to reconstruct CREATE TABLE statements
2026-06-28 16:44 UTC Rui Zhao <zhaorui126@gmail.com>
` Re: [PATCH] Add pg_get_table_ddl() to reconstruct CREATE TABLE statements
2026-06-29 10:40 UTC Akshay Joshi <akshay.joshi@enterprisedb.com>
` Re: [PATCH] Add pg_get_table_ddl() to reconstruct CREATE TABLE statements
2026-06-29 13:38 UTC Akshay Joshi <akshay.joshi@enterprisedb.com>
` Re: [PATCH] Add pg_get_table_ddl() to reconstruct CREATE TABLE statements
2026-06-29 21:31 UTC Zsolt Parragi <zsolt.parragi@percona.com>
` Re: [PATCH] Add pg_get_table_ddl() to reconstruct CREATE TABLE statements
2026-07-01 14:12 UTC Akshay Joshi <akshay.joshi@enterprisedb.com>
` Re: [PATCH] Add pg_get_table_ddl() to reconstruct CREATE TABLE statements
2026-07-01 15:10 UTC Marcos Pegoraro <marcos@f10.com.br>
` Re: [PATCH] Add pg_get_table_ddl() to reconstruct CREATE TABLE statements
2026-07-01 22:19 UTC Zsolt Parragi <zsolt.parragi@percona.com>
` Re: [PATCH] Add pg_get_table_ddl() to reconstruct CREATE TABLE statements
2026-07-02 02:17 UTC Kyotaro Horiguchi <horikyota.ntt@gmail.com>
` Re: [PATCH] Add pg_get_table_ddl() to reconstruct CREATE TABLE statements
2026-07-02 07:48 UTC Akshay Joshi <akshay.joshi@enterprisedb.com>
` Re: [PATCH] Add pg_get_table_ddl() to reconstruct CREATE TABLE statements
2026-07-02 08:48 UTC Akshay Joshi <akshay.joshi@enterprisedb.com>
` Re: [PATCH] Add pg_get_table_ddl() to reconstruct CREATE TABLE statements
2026-07-02 10:39 UTC Akshay Joshi <akshay.joshi@enterprisedb.com>
` Re: [PATCH] Add pg_get_table_ddl() to reconstruct CREATE TABLE statements
2026-07-02 16:35 UTC Marcos Pegoraro <marcos@f10.com.br>
` Re: [PATCH] Add pg_get_table_ddl() to reconstruct CREATE TABLE statements
2026-07-02 22:34 UTC Zsolt Parragi <zsolt.parragi@percona.com>
` Re: [PATCH] Add pg_get_table_ddl() to reconstruct CREATE TABLE statements
2026-07-03 08:47 UTC Akshay Joshi <akshay.joshi@enterprisedb.com>
` Re: [PATCH] Add pg_get_table_ddl() to reconstruct CREATE TABLE statements
2026-07-04 16:35 UTC Rui Zhao <zhaorui126@gmail.com>
` Re: [PATCH] Add pg_get_table_ddl() to reconstruct CREATE TABLE statements
2026-07-06 10:57 UTC Akshay Joshi <akshay.joshi@enterprisedb.com>
` Re: [PATCH] Add pg_get_table_ddl() to reconstruct CREATE TABLE statements
2026-07-07 16:53 UTC Rui Zhao <zhaorui126@gmail.com>
` Re: [PATCH] Add pg_get_table_ddl() to reconstruct CREATE TABLE statements
2026-07-08 11:56 UTC Akshay Joshi <akshay.joshi@enterprisedb.com>
` Re: [PATCH] Add pg_get_table_ddl() to reconstruct CREATE TABLE statements
2026-07-08 13:58 UTC Marcos Pegoraro <marcos@f10.com.br>
` Re: [PATCH] Add pg_get_table_ddl() to reconstruct CREATE TABLE statements
2026-07-09 08:53 UTC Akshay Joshi <akshay.joshi@enterprisedb.com>
` Re: [PATCH] Add pg_get_table_ddl() to reconstruct CREATE TABLE statements
2026-07-10 04:36 UTC Rui Zhao <zhaorui126@gmail.com>
` Re: [PATCH] Add pg_get_table_ddl() to reconstruct CREATE TABLE statements
2026-07-11 19:22 UTC Marcos Pegoraro <marcos@f10.com.br>
` Re: [PATCH] Add pg_get_table_ddl() to reconstruct CREATE TABLE statements
2026-07-13 10:05 UTC Akshay Joshi <akshay.joshi@enterprisedb.com>
` Re: [PATCH] Add pg_get_table_ddl() to reconstruct CREATE TABLE statements
2026-07-13 11:49 UTC Akshay Joshi <akshay.joshi@enterprisedb.com>
` Re: [PATCH] Add pg_get_table_ddl() to reconstruct CREATE TABLE statements
2026-07-13 23:01 UTC Zsolt Parragi <zsolt.parragi@percona.com>
` Re: [PATCH] Add pg_get_table_ddl() to reconstruct CREATE TABLE statements
2026-07-14 09:56 UTC Akshay Joshi <akshay.joshi@enterprisedb.com>
` Re: [PATCH] Add pg_get_table_ddl() to reconstruct CREATE TABLE statements
2026-07-15 21:09 UTC Zsolt Parragi <zsolt.parragi@percona.com>
` Re: [PATCH] Add pg_get_table_ddl() to reconstruct CREATE TABLE statements
2026-07-16 09:30 UTC Akshay Joshi <akshay.joshi@enterprisedb.com>
` Re: [PATCH] Add pg_get_table_ddl() to reconstruct CREATE TABLE statements
2026-07-21 19:41 UTC Zsolt Parragi <zsolt.parragi@percona.com>
` Re: [PATCH] Add pg_get_table_ddl() to reconstruct CREATE TABLE statements
2026-07-24 07:18 UTC Rui Zhao <zhaorui126@gmail.com>
` Re: [PATCH] Add pg_get_table_ddl() to reconstruct CREATE TABLE statements
2026-07-27 10:34 UTC Akshay Joshi <akshay.joshi@enterprisedb.com>
` Re: [PATCH] Add pg_get_table_ddl() to reconstruct CREATE TABLE statements
2026-07-29 16:07 UTC Rui Zhao <zhaorui126@gmail.com>
` Re: [PATCH] Add pg_get_table_ddl() to reconstruct CREATE TABLE statements
2026-08-05 08:21 UTC Akshay Joshi <akshay.joshi@enterprisedb.com>
` Re: [PATCH] Add pg_get_table_ddl() to reconstruct CREATE TABLE statements
2026-08-11 11:51 UTC Rui Zhao <zhaorui126@gmail.com>
` Re: [PATCH] Add pg_get_table_ddl() to reconstruct CREATE TABLE statements
2026-08-31 11:49 UTC Akshay Joshi <akshay.joshi@enterprisedb.com>
` Re: [PATCH] Add pg_get_table_ddl() to reconstruct CREATE TABLE statements
2026-09-08 15:19 UTC Rui Zhao <zhaorui126@gmail.com>
` Re: [PATCH] Add pg_get_table_ddl() to reconstruct CREATE TABLE statements
2026-09-23 13:00 UTC Akshay Joshi <akshay.joshi@enterprisedb.com>
` Re: [PATCH] Add pg_get_table_ddl() to reconstruct CREATE TABLE statements
2026-09-23 18:13 UTC Marcos Pegoraro <marcos@f10.com.br>
` Re: [PATCH] Add pg_get_table_ddl() to reconstruct CREATE TABLE statements
2026-10-02 03:53 UTC Henson Choi <assam258@gmail.com>
[73+ messages in thread]
Server crash when describing a FETCH statement after its cursor is closed
2026-09-25 11:29 UTC Dirkjan Bussink <d.bussink@gmail.com>
` Re: Server crash when describing a FETCH statement after its cursor is closed
2026-09-25 14:33 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: Server crash when describing a FETCH statement after its cursor is closed
2026-09-25 18:27 UTC Dirkjan Bussink <d.bussink@gmail.com>
` Re: Server crash when describing a FETCH statement after its cursor is closed
2026-09-26 07:23 UTC Dirkjan Bussink <d.bussink@gmail.com>
` Re: Server crash when describing a FETCH statement after its cursor is closed
2026-10-01 05:26 UTC Michael Paquier <michael@paquier.xyz>
` Re: Server crash when describing a FETCH statement after its cursor is closed
2026-10-02 01:50 UTC Michael Paquier <michael@paquier.xyz>
[6+ messages in thread]
Extension-defined restore actions depending on dumped objects
2026-10-02 01:46 UTC Haibo Yan <tristan.yim@gmail.com>
[PATCH v2 4/4] Refactor some SIMD and popcount macros.
2026-01-15 18:26 UTC Nathan Bossart <nathan@postgresql.org>
` Report index currently being vacuumed in pg_stat_progress_vacuum
2026-05-04 02:00 UTC Bharath Rupireddy <bharath.rupireddyforpostgres@gmail.com>
` Re: Report index currently being vacuumed in pg_stat_progress_vacuum
2026-05-04 04:53 UTC SATYANARAYANA NARLAPURAM <satyanarlapuram@gmail.com>
` Re: Report index currently being vacuumed in pg_stat_progress_vacuum
2026-05-04 09:52 UTC Antonin Houska <ah@cybertec.at>
` Re: Report index currently being vacuumed in pg_stat_progress_vacuum
2026-05-05 17:54 UTC Sami Imseih <samimseih@gmail.com>
` Re: Report index currently being vacuumed in pg_stat_progress_vacuum
2026-06-29 15:31 UTC Bharath Rupireddy <bharath.rupireddyforpostgres@gmail.com>
` Re: Report index currently being vacuumed in pg_stat_progress_vacuum
2026-07-16 20:49 UTC Sami Imseih <samimseih@gmail.com>
` Re: Report index currently being vacuumed in pg_stat_progress_vacuum
2026-07-17 19:24 UTC Sami Imseih <samimseih@gmail.com>
` Re: Report index currently being vacuumed in pg_stat_progress_vacuum
2026-08-04 22:20 UTC Bharath Rupireddy <bharath.rupireddyforpostgres@gmail.com>
` Re: Report index currently being vacuumed in pg_stat_progress_vacuum
2026-08-12 21:45 UTC Sami Imseih <samimseih@gmail.com>
` Re: Report index currently being vacuumed in pg_stat_progress_vacuum
2026-08-13 23:30 UTC Bharath Rupireddy <bharath.rupireddyforpostgres@gmail.com>
` Re: Report index currently being vacuumed in pg_stat_progress_vacuum
2026-08-14 00:47 UTC Sami Imseih <samimseih@gmail.com>
` Re: Report index currently being vacuumed in pg_stat_progress_vacuum
2026-08-14 03:33 UTC Michael Paquier <michael@paquier.xyz>
` Re: Report index currently being vacuumed in pg_stat_progress_vacuum
2026-08-14 03:48 UTC Michael Paquier <michael@paquier.xyz>
` Re: Report index currently being vacuumed in pg_stat_progress_vacuum
2026-08-14 21:26 UTC Sami Imseih <samimseih@gmail.com>
` Re: Report index currently being vacuumed in pg_stat_progress_vacuum
2026-08-14 23:35 UTC Sami Imseih <samimseih@gmail.com>
` Re: Report index currently being vacuumed in pg_stat_progress_vacuum
2026-08-19 18:10 UTC Bharath Rupireddy <bharath.rupireddyforpostgres@gmail.com>
` Re: Report index currently being vacuumed in pg_stat_progress_vacuum
2026-08-19 18:31 UTC Sami Imseih <samimseih@gmail.com>
` Re: Report index currently being vacuumed in pg_stat_progress_vacuum
2026-08-20 02:37 UTC Bharath Rupireddy <bharath.rupireddyforpostgres@gmail.com>
` Re: Report index currently being vacuumed in pg_stat_progress_vacuum
2026-08-20 23:10 UTC Michael Paquier <michael@paquier.xyz>
` Re: Report index currently being vacuumed in pg_stat_progress_vacuum
2026-08-20 23:58 UTC Sami Imseih <samimseih@gmail.com>
` Re: Report index currently being vacuumed in pg_stat_progress_vacuum
2026-08-25 16:34 UTC Bharath Rupireddy <bharath.rupireddyforpostgres@gmail.com>
` Re: Report index currently being vacuumed in pg_stat_progress_vacuum
2026-09-03 02:23 UTC Bharath Rupireddy <bharath.rupireddyforpostgres@gmail.com>
` Re: Report index currently being vacuumed in pg_stat_progress_vacuum
2026-09-03 05:15 UTC Michael Paquier <michael@paquier.xyz>
` Re: Report index currently being vacuumed in pg_stat_progress_vacuum
2026-09-03 16:49 UTC Sami Imseih <samimseih.pg@gmail.com>
` Re: Report index currently being vacuumed in pg_stat_progress_vacuum
2026-09-09 19:01 UTC Masahiko Sawada <sawada.mshk@gmail.com>
` Re: Report index currently being vacuumed in pg_stat_progress_vacuum
2026-09-14 20:28 UTC Bharath Rupireddy <bharath.rupireddyforpostgres@gmail.com>
` Re: Report index currently being vacuumed in pg_stat_progress_vacuum
2026-09-15 17:10 UTC Sami Imseih <samimseih.pg@gmail.com>
` Re: Report index currently being vacuumed in pg_stat_progress_vacuum
2026-09-15 22:28 UTC Bharath Rupireddy <bharath.rupireddyforpostgres@gmail.com>
` Re: Report index currently being vacuumed in pg_stat_progress_vacuum
2026-09-17 02:23 UTC shihao zhong <zhong950419@gmail.com>
` Re: Report index currently being vacuumed in pg_stat_progress_vacuum
2026-09-17 23:00 UTC Michael Paquier <michael@paquier.xyz>
` Re: Report index currently being vacuumed in pg_stat_progress_vacuum
2026-09-18 01:00 UTC shihao zhong <zhong950419@gmail.com>
` Re: Report index currently being vacuumed in pg_stat_progress_vacuum
2026-09-18 18:23 UTC Bharath Rupireddy <bharath.rupireddyforpostgres@gmail.com>
` Re: Report index currently being vacuumed in pg_stat_progress_vacuum
2026-10-01 00:37 UTC Michael Paquier <michael@paquier.xyz>
` Re: Report index currently being vacuumed in pg_stat_progress_vacuum
2026-10-01 01:55 UTC Michael Paquier <michael@paquier.xyz>
` Re: Report index currently being vacuumed in pg_stat_progress_vacuum
2026-10-01 03:16 UTC Sami Imseih <samimseih.pg@gmail.com>
` Re: Report index currently being vacuumed in pg_stat_progress_vacuum
2026-10-01 03:18 UTC shihao zhong <zhong950419@gmail.com>
` Re: Report index currently being vacuumed in pg_stat_progress_vacuum
2026-10-01 04:23 UTC Michael Paquier <michael@paquier.xyz>
` Re: Report index currently being vacuumed in pg_stat_progress_vacuum
2026-10-01 05:20 UTC Bharath Rupireddy <bharath.rupireddyforpostgres@gmail.com>
` Re: Report index currently being vacuumed in pg_stat_progress_vacuum
2026-10-01 22:45 UTC Michael Paquier <michael@paquier.xyz>
[40+ messages in thread]
[Patch] Batch fsyncs when recycling WAL segments
2026-08-02 10:48 UTC Ayush Tiwari <ayushtiwari.slg01@gmail.com>
` Re: [Patch] Batch fsyncs when recycling WAL segments
2026-08-18 18:52 UTC Ayush Tiwari <ayushtiwari.slg01@gmail.com>
` Re: [Patch] Batch fsyncs when recycling WAL segments
2026-09-02 18:57 UTC Ayush Tiwari <ayushtiwari.slg01@gmail.com>
` Re: [Patch] Batch fsyncs when recycling WAL segments
2026-10-01 22:16 UTC Ayush Tiwari <ayushtiwari.slg01@gmail.com>
[4+ messages in thread]
COMMENTS are not being copied in CREATE TABLE LIKE
2026-02-12 10:11 UTC Jim Jones <jim.jones@uni-muenster.de>
` Re: COMMENTS are not being copied in CREATE TABLE LIKE
2026-02-12 14:36 UTC Matheus Alcantara <matheusssilv97@gmail.com>
` Re: COMMENTS are not being copied in CREATE TABLE LIKE
2026-02-12 15:08 UTC Fujii Masao <masao.fujii@gmail.com>
` Re: COMMENTS are not being copied in CREATE TABLE LIKE
2026-02-12 15:33 UTC Jim Jones <jim.jones@uni-muenster.de>
` Re: COMMENTS are not being copied in CREATE TABLE LIKE
2026-02-12 16:25 UTC Matheus Alcantara <matheusssilv97@gmail.com>
` Re: COMMENTS are not being copied in CREATE TABLE LIKE
2026-02-13 01:29 UTC Chao Li <li.evan.chao@gmail.com>
` Re: COMMENTS are not being copied in CREATE TABLE LIKE
2026-02-13 04:13 UTC Fujii Masao <masao.fujii@gmail.com>
` Re: COMMENTS are not being copied in CREATE TABLE LIKE
2026-02-13 04:22 UTC David G. Johnston <david.g.johnston@gmail.com>
` Re: COMMENTS are not being copied in CREATE TABLE LIKE
2026-02-13 04:30 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: COMMENTS are not being copied in CREATE TABLE LIKE
2026-02-13 09:19 UTC Jim Jones <jim.jones@uni-muenster.de>
` Re: COMMENTS are not being copied in CREATE TABLE LIKE
2026-02-22 08:05 UTC Hüseyin Demir <huseyin.d3r@gmail.com>
` Re: COMMENTS are not being copied in CREATE TABLE LIKE
2026-02-22 12:34 UTC Jim Jones <jim.jones@uni-muenster.de>
` Re: COMMENTS are not being copied in CREATE TABLE LIKE
2026-02-26 07:46 UTC Hüseyin Demir <huseyin.d3r@gmail.com>
` Re: COMMENTS are not being copied in CREATE TABLE LIKE
2026-02-26 10:07 UTC Jim Jones <jim.jones@uni-muenster.de>
` Re: COMMENTS are not being copied in CREATE TABLE LIKE
2026-02-26 13:39 UTC Jim Jones <jim.jones@uni-muenster.de>
` Re: COMMENTS are not being copied in CREATE TABLE LIKE
2026-03-24 18:32 UTC Carlos Alves <carlos@alves.inf.br>
` Re: COMMENTS are not being copied in CREATE TABLE LIKE
2026-03-25 09:21 UTC Jim Jones <jim.jones@uni-muenster.de>
` Re: COMMENTS are not being copied in CREATE TABLE LIKE
2026-03-25 13:59 UTC Carlos Alves <carlos@alves.inf.br>
` Re: COMMENTS are not being copied in CREATE TABLE LIKE
2026-03-26 17:59 UTC Carlos Alves <carlos@alves.inf.br>
` Re: COMMENTS are not being copied in CREATE TABLE LIKE
2026-03-26 18:12 UTC Jim Jones <jim.jones@uni-muenster.de>
` Re: COMMENTS are not being copied in CREATE TABLE LIKE
2026-07-18 14:03 UTC ZizhuanLiu X-MAN <44973863@qq.com>
` Re: COMMENTS are not being copied in CREATE TABLE LIKE
2026-07-20 11:52 UTC Jim Jones <jim.jones@uni-muenster.de>
` Re: COMMENTS are not being copied in CREATE TABLE LIKE
2026-07-20 13:24 UTC ZizhuanLiu X-MAN <44973863@qq.com>
` Re: COMMENTS are not being copied in CREATE TABLE LIKE
2026-07-23 11:51 UTC Jim Jones <jim.jones@uni-muenster.de>
` Re: COMMENTS are not being copied in CREATE TABLE LIKE
2026-07-24 02:01 UTC ZizhuanLiu X-MAN <44973863@qq.com>
` Re: COMMENTS are not being copied in CREATE TABLE LIKE
2026-07-24 07:07 UTC ZizhuanLiu X-MAN <44973863@qq.com>
` Re: COMMENTS are not being copied in CREATE TABLE LIKE
2026-09-20 20:28 UTC Alex Liapychev <coder.sam@gmail.com>
` Re: COMMENTS are not being copied in CREATE TABLE LIKE
2026-09-21 13:58 UTC Tomas Vondra <tomas@vondra.me>
` Re: COMMENTS are not being copied in CREATE TABLE LIKE
2026-09-22 19:49 UTC Jim Jones <jim.jones@uni-muenster.de>
` Re: COMMENTS are not being copied in CREATE TABLE LIKE
2026-09-27 00:23 UTC Alex Liapychev <coder.sam@gmail.com>
` Re: COMMENTS are not being copied in CREATE TABLE LIKE
2026-09-30 23:14 UTC Alex Liapychev <coder.sam@gmail.com>
` Re: COMMENTS are not being copied in CREATE TABLE LIKE
2026-10-01 16:49 UTC Jim Jones <jim.jones@uni-muenster.de>
` Re: COMMENTS are not being copied in CREATE TABLE LIKE
2026-10-01 17:25 UTC Tomas Vondra <tomas@vondra.me>
` Re: COMMENTS are not being copied in CREATE TABLE LIKE
2026-10-01 17:45 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: COMMENTS are not being copied in CREATE TABLE LIKE
2026-10-01 21:13 UTC Alex Liapychev <coder.sam@gmail.com>
` Re: COMMENTS are not being copied in CREATE TABLE LIKE
2026-10-01 21:30 UTC Jim Jones <jim.jones@uni-muenster.de>
` Re: COMMENTS are not being copied in CREATE TABLE LIKE
2026-10-01 21:36 UTC Jim Jones <jim.jones@uni-muenster.de>
[37+ messages in thread]
REPACK (CONCURRENTLY) can crash a logical decoding session
2026-09-02 11:48 UTC Thom Brown <thom@linux.com>
` Re: REPACK (CONCURRENTLY) can crash a logical decoding session
2026-09-02 18:19 UTC Antonin Houska <ah@cybertec.at>
` Re: REPACK (CONCURRENTLY) can crash a logical decoding session
2026-09-04 13:11 UTC Thom Brown <thom@linux.com>
` Re: REPACK (CONCURRENTLY) can crash a logical decoding session
2026-09-05 06:17 UTC Masahiko Sawada <sawada.mshk@gmail.com>
` RE: REPACK (CONCURRENTLY) can crash a logical decoding session
2026-09-06 16:18 UTC Zhijie Hou (Fujitsu) <houzj.fnst@fujitsu.com>
` Re: REPACK (CONCURRENTLY) can crash a logical decoding session
2026-09-08 21:12 UTC Masahiko Sawada <sawada.mshk@gmail.com>
` Re: REPACK (CONCURRENTLY) can crash a logical decoding session
2026-09-10 17:37 UTC Masahiko Sawada <sawada.mshk@gmail.com>
` Re: REPACK (CONCURRENTLY) can crash a logical decoding session
2026-09-11 12:02 UTC Álvaro Herrera <alvherre@kurilemu.de>
` Re: REPACK (CONCURRENTLY) can crash a logical decoding session
2026-09-11 17:56 UTC Masahiko Sawada <sawada.mshk@gmail.com>
` Re: REPACK (CONCURRENTLY) can crash a logical decoding session
2026-09-29 20:00 UTC Alexander Lakhin <exclusion@gmail.com>
` Re: REPACK (CONCURRENTLY) can crash a logical decoding session
2026-09-30 17:19 UTC Masahiko Sawada <sawada.mshk@gmail.com>
` Re: REPACK (CONCURRENTLY) can crash a logical decoding session
2026-10-01 18:30 UTC Masahiko Sawada <sawada.mshk@gmail.com>
[12+ messages in thread]
REPACK enhancements
2026-06-16 12:53 UTC Antonin Houska <ah@cybertec.at>
` Re: REPACK enhancements
2026-07-15 08:47 UTC Antonin Houska <ah@cybertec.at>
` Re: REPACK enhancements
2026-09-15 04:20 UTC shihao zhong <zhong950419@gmail.com>
` Re: REPACK enhancements
2026-09-16 16:59 UTC Antonin Houska <ah@cybertec.at>
` Re: REPACK enhancements
2026-09-17 02:03 UTC shihao zhong <zhong950419@gmail.com>
` Re: REPACK enhancements
2026-09-17 16:36 UTC Antonin Houska <ah@cybertec.at>
` Re: REPACK enhancements
2026-09-18 18:38 UTC Antonin Houska <ah@cybertec.at>
` Re: REPACK enhancements
2026-09-21 23:27 UTC shihao zhong <zhong950419@gmail.com>
` Re: REPACK enhancements
2026-09-22 03:34 UTC Manu <manuelreyesbravo@gmail.com>
` Re: REPACK enhancements
2026-09-23 10:06 UTC Antonin Houska <ah@cybertec.at>
` Re: REPACK enhancements
2026-09-23 14:17 UTC Manu <manuelreyesbravo@gmail.com>
` Re: REPACK enhancements
2026-09-24 10:55 UTC Antonin Houska <ah@cybertec.at>
` Re: REPACK enhancements
2026-09-24 13:32 UTC shihao zhong <zhong950419@gmail.com>
` Re: REPACK enhancements
2026-09-24 14:02 UTC Antonin Houska <ah@cybertec.at>
` Re: REPACK enhancements
2026-09-30 16:58 UTC Antonin Houska <ah@cybertec.at>
` Re: REPACK enhancements
2026-10-01 03:28 UTC shihao zhong <zhong950419@gmail.com>
` Re: REPACK enhancements
2026-10-01 18:29 UTC Antonin Houska <ah@cybertec.at>
[17+ messages in thread]
Proposal: JSON5 support in the JSON parsers
2026-07-14 23:10 UTC Zsolt Parragi <zsolt.parragi@percona.com>
` Re: Proposal: JSON5 support in the JSON parsers
2026-10-01 07:59 UTC Zsolt Parragi <zsolt.parragi@percona.com>
[2+ messages in thread]
Re: BUG #19599: RestoreBlockImage: the decode cross-checks never bound hole_offset + hole_length against BLCKSZ
2026-09-04 08:01 UTC Grigorev Jurij <ju.grigorev@ftdata.ru>
` Re: BUG #19599: RestoreBlockImage: the decode cross-checks never bound hole_offset + hole_length against BLCKSZ
2026-09-26 16:54 UTC Rahul Yadav <rahul@rhyadav.com>
` Re: BUG #19599: RestoreBlockImage: the decode cross-checks never bound hole_offset + hole_length against BLCKSZ
2026-09-29 08:37 UTC Grigorev Jurij <ju.grigorev@ftdata.ru>
` Re: BUG #19599: RestoreBlockImage: the decode cross-checks never bound hole_offset + hole_length against BLCKSZ
2026-09-30 10:07 UTC Rahul Yadav <rahul@rhyadav.com>
` Re: BUG #19599: RestoreBlockImage: the decode cross-checks never bound hole_offset + hole_length against BLCKSZ
2026-09-30 23:53 UTC Michael Paquier <michael@paquier.xyz>
` Re: BUG #19599: RestoreBlockImage: the decode cross-checks never bound hole_offset + hole_length against BLCKSZ
2026-10-01 03:18 UTC Grigorev Jurij <ju.grigorev@ftdata.ru>
[6+ messages in thread]
Document that jsonpath == can be used as ANY
2026-08-17 12:04 UTC Marcos Pegoraro <marcos@f10.com.br>
` Re: Document that jsonpath == can be used as ANY
2026-09-30 18:47 UTC Marcos Pegoraro <marcos@f10.com.br>
` Re: Document that jsonpath == can be used as ANY
2026-09-30 19:13 UTC David G. Johnston <david.g.johnston@gmail.com>
` Re: Document that jsonpath == can be used as ANY
2026-09-30 20:21 UTC Marcos Pegoraro <marcos@f10.com.br>
` Re: Document that jsonpath == can be used as ANY
2026-10-01 00:34 UTC David G. Johnston <david.g.johnston@gmail.com>
[5+ messages in thread]
Support for 8-byte TOAST values, round two
2026-05-08 06:07 UTC Michael Paquier <michael@paquier.xyz>
` Re: Support for 8-byte TOAST values, round two
2026-07-30 04:38 UTC Yugo Nagata <nagata@sraoss.co.jp>
` Re: Support for 8-byte TOAST values, round two
2026-07-30 08:01 UTC Yugo Nagata <nagata@sraoss.co.jp>
` Re: Support for 8-byte TOAST values, round two
2026-07-30 11:16 UTC Hannu Krosing <hannuk@google.com>
` Re: Support for 8-byte TOAST values, round two
2026-07-31 02:36 UTC Michael Paquier <michael@paquier.xyz>
` Re: Support for 8-byte TOAST values, round two
2026-07-31 10:58 UTC Hannu Krosing <hannuk@google.com>
` Re: Support for 8-byte TOAST values, round two
2026-07-31 11:10 UTC Matthias van de Meent <boekewurm+postgres@gmail.com>
` Re: Support for 8-byte TOAST values, round two
2026-07-31 14:16 UTC Hannu Krosing <hannuk@google.com>
` Re: Support for 8-byte TOAST values, round two
2026-08-06 04:38 UTC Michael Paquier <michael@paquier.xyz>
` Re: Support for 8-byte TOAST values, round two
2026-08-09 21:53 UTC Hannu Krosing <hannuk@google.com>
` Re: Support for 8-byte TOAST values, round two
2026-08-10 00:08 UTC Michael Paquier <michael@paquier.xyz>
` Re: Support for 8-byte TOAST values, round two
2026-08-10 07:37 UTC Hannu Krosing <hannuk@google.com>
` Re: Support for 8-byte TOAST values, round two
2026-08-10 08:03 UTC Michael Paquier <michael@paquier.xyz>
` Re: Support for 8-byte TOAST values, round two
2026-08-10 10:43 UTC Hannu Krosing <hannuk@google.com>
` Re: Support for 8-byte TOAST values, round two
2026-08-13 06:38 UTC Michael Paquier <michael@paquier.xyz>
` Re: Support for 8-byte TOAST values, round two
2026-09-02 20:27 UTC Bharath Rupireddy <bharath.rupireddyforpostgres@gmail.com>
` Re: Support for 8-byte TOAST values, round two
2026-09-03 04:58 UTC Michael Paquier <michael@paquier.xyz>
` Re: Support for 8-byte TOAST values, round two
2026-09-04 04:28 UTC Michael Paquier <michael@paquier.xyz>
` Re: Support for 8-byte TOAST values, round two
2026-09-05 03:11 UTC Bharath Rupireddy <bharath.rupireddyforpostgres@gmail.com>
` Re: Support for 8-byte TOAST values, round two
2026-09-07 07:54 UTC Michael Paquier <michael@paquier.xyz>
` Re: Support for 8-byte TOAST values, round two
2026-09-08 03:50 UTC Michael Paquier <michael@paquier.xyz>
` Re: Support for 8-byte TOAST values, round two
2026-09-08 23:55 UTC Bharath Rupireddy <bharath.rupireddyforpostgres@gmail.com>
` Re: Support for 8-byte TOAST values, round two
2026-09-09 00:58 UTC Michael Paquier <michael@paquier.xyz>
` Re: Support for 8-byte TOAST values, round two
2026-09-09 14:14 UTC Greg Burd <greg@burd.me>
` Re: Support for 8-byte TOAST values, round two
2026-09-09 17:13 UTC Bharath Rupireddy <bharath.rupireddyforpostgres@gmail.com>
` Re: Support for 8-byte TOAST values, round two
2026-09-09 17:14 UTC Greg Burd <greg@burd.me>
` Re: Support for 8-byte TOAST values, round two
2026-09-09 23:18 UTC Michael Paquier <michael@paquier.xyz>
` Re: Support for 8-byte TOAST values, round two
2026-09-10 07:51 UTC Michael Paquier <michael@paquier.xyz>
` Re: Support for 8-byte TOAST values, round two
2026-09-10 17:06 UTC Bharath Rupireddy <bharath.rupireddyforpostgres@gmail.com>
` Re: Support for 8-byte TOAST values, round two
2026-09-10 21:14 UTC Bharath Rupireddy <bharath.rupireddyforpostgres@gmail.com>
` Re: Support for 8-byte TOAST values, round two
2026-09-11 03:42 UTC Michael Paquier <michael@paquier.xyz>
` Re: Support for 8-byte TOAST values, round two
2026-09-11 07:33 UTC Michael Paquier <michael@paquier.xyz>
` Re: Support for 8-byte TOAST values, round two
2026-09-11 15:44 UTC Bharath Rupireddy <bharath.rupireddyforpostgres@gmail.com>
` Re: Support for 8-byte TOAST values, round two
2026-09-11 16:03 UTC Marcos Pegoraro <marcos@f10.com.br>
` Re: Support for 8-byte TOAST values, round two
2026-09-11 17:07 UTC Bharath Rupireddy <bharath.rupireddyforpostgres@gmail.com>
` Re: Support for 8-byte TOAST values, round two
2026-09-11 17:38 UTC Rui Zhao <zhaorui126@gmail.com>
` Re: Support for 8-byte TOAST values, round two
2026-09-11 23:30 UTC Michael Paquier <michael@paquier.xyz>
` Re: Support for 8-byte TOAST values, round two
2026-09-12 17:46 UTC Rui Zhao <zhaorui126@gmail.com>
` Re: Support for 8-byte TOAST values, round two
2026-09-13 16:22 UTC Oleg Bartunov <obartunov@postgrespro.ru>
` Re: Support for 8-byte TOAST values, round two
2026-09-13 23:17 UTC Michael Paquier <michael@paquier.xyz>
` Re: Support for 8-byte TOAST values, round two
2026-09-13 23:51 UTC Michael Paquier <michael@paquier.xyz>
` Re: Support for 8-byte TOAST values, round two
2026-09-14 00:46 UTC Michael Paquier <michael@paquier.xyz>
` Re: Support for 8-byte TOAST values, round two
2026-09-14 01:39 UTC Oleg Bartunov <obartunov@postgrespro.ru>
` Re: Support for 8-byte TOAST values, round two
2026-09-14 02:16 UTC Michael Paquier <michael@paquier.xyz>
` Re: Support for 8-byte TOAST values, round two
2026-09-14 05:00 UTC Michael Paquier <michael@paquier.xyz>
` Re: Support for 8-byte TOAST values, round two
2026-09-14 05:12 UTC Michael Paquier <michael@paquier.xyz>
` Re: Support for 8-byte TOAST values, round two
2026-09-14 14:01 UTC Greg Burd <greg@burd.me>
` Re: Support for 8-byte TOAST values, round two
2026-09-14 19:26 UTC Bharath Rupireddy <bharath.rupireddyforpostgres@gmail.com>
` Re: Support for 8-byte TOAST values, round two
2026-09-14 23:43 UTC Bharath Rupireddy <bharath.rupireddyforpostgres@gmail.com>
` Re: Support for 8-byte TOAST values, round two
2026-09-15 07:08 UTC Michael Paquier <michael@paquier.xyz>
` Re: Support for 8-byte TOAST values, round two
2026-09-15 07:59 UTC Michael Paquier <michael@paquier.xyz>
` Re: Support for 8-byte TOAST values, round two
2026-09-15 15:26 UTC Greg Burd <greg@burd.me>
` Re: Support for 8-byte TOAST values, round two
2026-09-15 16:20 UTC Rui Zhao <zhaorui126@gmail.com>
` Re: Support for 8-byte TOAST values, round two
2026-09-15 17:05 UTC Greg Burd <greg@burd.me>
` Re: Support for 8-byte TOAST values, round two
2026-09-15 22:22 UTC Bharath Rupireddy <bharath.rupireddyforpostgres@gmail.com>
` Re: Support for 8-byte TOAST values, round two
2026-09-16 00:29 UTC Michael Paquier <michael@paquier.xyz>
` Re: Support for 8-byte TOAST values, round two
2026-09-16 00:34 UTC Michael Paquier <michael@paquier.xyz>
` Re: Support for 8-byte TOAST values, round two
2026-09-16 01:59 UTC Michael Paquier <michael@paquier.xyz>
` Re: Support for 8-byte TOAST values, round two
2026-09-16 17:48 UTC Bharath Rupireddy <bharath.rupireddyforpostgres@gmail.com>
` Re: Support for 8-byte TOAST values, round two
2026-09-16 23:50 UTC Michael Paquier <michael@paquier.xyz>
` Re: Support for 8-byte TOAST values, round two
2026-09-17 19:03 UTC Bharath Rupireddy <bharath.rupireddyforpostgres@gmail.com>
` Re: Support for 8-byte TOAST values, round two
2026-09-19 00:03 UTC Michael Paquier <michael@paquier.xyz>
` Re: Support for 8-byte TOAST values, round two
2026-09-19 00:26 UTC Bharath Rupireddy <bharath.rupireddyforpostgres@gmail.com>
` Re: Support for 8-byte TOAST values, round two
2026-09-21 11:11 UTC John Naylor <johncnaylorls@gmail.com>
` Re: Support for 8-byte TOAST values, round two
2026-09-21 22:39 UTC Bharath Rupireddy <bharath.rupireddyforpostgres@gmail.com>
` Re: Support for 8-byte TOAST values, round two
2026-09-21 22:53 UTC Michael Paquier <michael@paquier.xyz>
` Re: Support for 8-byte TOAST values, round two
2026-09-22 00:07 UTC Bharath Rupireddy <bharath.rupireddyforpostgres@gmail.com>
` Re: Support for 8-byte TOAST values, round two
2026-09-22 07:57 UTC Michael Paquier <michael@paquier.xyz>
` Re: Support for 8-byte TOAST values, round two
2026-09-22 22:35 UTC Bharath Rupireddy <bharath.rupireddyforpostgres@gmail.com>
` Re: Support for 8-byte TOAST values, round two
2026-09-23 10:57 UTC Michael Paquier <michael@paquier.xyz>
` Re: Support for 8-byte TOAST values, round two
2026-09-30 10:44 UTC Hannu Krosing <hannuk@google.com>
` Re: Support for 8-byte TOAST values, round two
2026-09-30 23:22 UTC Michael Paquier <michael@paquier.xyz>
[72+ messages in thread]
WITHOUT OVERLAPS foreign key allows referencing EXCLUDE constraint
2026-09-30 21:41 UTC Paul A Jungwirth <pj@illuminatedcomputing.com>
Do we need to back-patch tzcode 2026b after all?
2026-09-30 02:21 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: Do we need to back-patch tzcode 2026b after all?
2026-09-30 12:19 UTC Daniel Gustafsson <daniel@yesql.se>
` Re: Do we need to back-patch tzcode 2026b after all?
2026-09-30 21:01 UTC Tom Lane <tgl@sss.pgh.pa.us>
[3+ messages in thread]
Open SSI correctness issues
2026-08-28 13:00 UTC Andrey Borodin <x4mmm@yandex-team.ru>
` Re: Open SSI correctness issues
2026-09-17 08:45 UTC Andrey Borodin <x4mmm@yandex-team.ru>
` Re: Open SSI correctness issues
2026-09-21 12:01 UTC Aleksander Alekseev <aleksander@tigerdata.com>
` Re: Open SSI correctness issues
2026-09-30 12:36 UTC Aleksander Alekseev <aleksander@tigerdata.com>
` Re: Open SSI correctness issues
2026-09-30 17:41 UTC Andrey Borodin <x4mmm@yandex-team.ru>
` Re: Open SSI correctness issues
2026-09-30 20:15 UTC Aleksander Alekseev <aleksander@tigerdata.com>
[6+ messages in thread]
Residual cleanups for tied objects in PL/Perl
2026-08-16 17:38 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: Residual cleanups for tied objects in PL/Perl
2026-08-16 18:47 UTC Andrew Dunstan <andrew@dunslane.net>
` Re: Residual cleanups for tied objects in PL/Perl
2026-08-16 19:04 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: Residual cleanups for tied objects in PL/Perl
2026-08-16 20:08 UTC Andrey Rachitskiy <pl0h0yp1@gmail.com>
` Re: Residual cleanups for tied objects in PL/Perl
2026-08-16 20:26 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: Residual cleanups for tied objects in PL/Perl
2026-08-16 21:10 UTC Andrew Dunstan <andrew@dunslane.net>
` Re: Residual cleanups for tied objects in PL/Perl
2026-08-16 21:40 UTC Andrey Rachitskiy <pl0h0yp1@gmail.com>
` Re: Residual cleanups for tied objects in PL/Perl
2026-08-16 22:24 UTC Andrey Rachitskiy <pl0h0yp1@gmail.com>
` Re: Residual cleanups for tied objects in PL/Perl
2026-08-17 06:05 UTC Andrey Rachitskiy <pl0h0yp1@gmail.com>
` Re: Residual cleanups for tied objects in PL/Perl
2026-08-17 15:41 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: Residual cleanups for tied objects in PL/Perl
2026-08-17 16:49 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: Residual cleanups for tied objects in PL/Perl
2026-08-17 17:21 UTC Andrey Rachitskiy <pl0h0yp1@gmail.com>
` Re: Residual cleanups for tied objects in PL/Perl
2026-08-17 17:26 UTC Andrey Rachitskiy <pl0h0yp1@gmail.com>
` Re: Residual cleanups for tied objects in PL/Perl
2026-08-17 17:58 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: Residual cleanups for tied objects in PL/Perl
2026-08-17 18:08 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: Residual cleanups for tied objects in PL/Perl
2026-08-17 18:25 UTC Andrey Rachitskiy <pl0h0yp1@gmail.com>
` Re: Residual cleanups for tied objects in PL/Perl
2026-08-17 18:44 UTC Andrew Dunstan <andrew@dunslane.net>
` Re: Residual cleanups for tied objects in PL/Perl
2026-08-17 18:58 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: Residual cleanups for tied objects in PL/Perl
2026-08-17 19:07 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: Residual cleanups for tied objects in PL/Perl
2026-08-17 20:42 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: Residual cleanups for tied objects in PL/Perl
2026-08-18 05:27 UTC Andrey Rachitskiy <pl0h0yp1@gmail.com>
` Re: Residual cleanups for tied objects in PL/Perl
2026-08-18 11:58 UTC Andrey Rachitskiy <pl0h0yp1@gmail.com>
` Re: Residual cleanups for tied objects in PL/Perl
2026-08-18 15:17 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: Residual cleanups for tied objects in PL/Perl
2026-08-18 15:48 UTC Andrey Rachitskiy <pl0h0yp1@gmail.com>
` Re: Residual cleanups for tied objects in PL/Perl
2026-08-18 21:58 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: Residual cleanups for tied objects in PL/Perl
2026-08-19 18:09 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: Residual cleanups for tied objects in PL/Perl
2026-08-19 18:22 UTC Andrey Rachitskiy <pl0h0yp1@gmail.com>
` Re: Residual cleanups for tied objects in PL/Perl
2026-09-30 16:17 UTC Kirill Reshke <reshkekirill@gmail.com>
` Re: Residual cleanups for tied objects in PL/Perl
2026-09-30 18:35 UTC Andrey Rachitskiy <pl0h0yp1@gmail.com>
[29+ messages in thread]
Postmaster crashes on SIGHUP when oauth_validator_libraries holds only whitespace
2026-09-14 11:22 UTC Grigorev Jurij <ju.grigorev@ftdata.ru>
` Re: Postmaster crashes on SIGHUP when oauth_validator_libraries holds only whitespace
2026-09-14 11:28 UTC Daniel Gustafsson <daniel@yesql.se>
` Re: Postmaster crashes on SIGHUP when oauth_validator_libraries holds only whitespace
2026-09-14 21:28 UTC Jacob Champion <jacob.champion@enterprisedb.com>
` Re: Postmaster crashes on SIGHUP when oauth_validator_libraries holds only whitespace
2026-09-14 21:34 UTC Daniel Gustafsson <daniel@yesql.se>
` Re: Postmaster crashes on SIGHUP when oauth_validator_libraries holds only whitespace
2026-09-15 02:55 UTC Grigorev Jurij <ju.grigorev@ftdata.ru>
` Re: Postmaster crashes on SIGHUP when oauth_validator_libraries holds only whitespace
2026-09-15 21:42 UTC Daniel Gustafsson <daniel@yesql.se>
` Re: Postmaster crashes on SIGHUP when oauth_validator_libraries holds only whitespace
2026-09-16 08:27 UTC Grigorev Jurij <ju.grigorev@ftdata.ru>
` Re: Postmaster crashes on SIGHUP when oauth_validator_libraries holds only whitespace
2026-09-16 22:16 UTC Jacob Champion <jacob.champion@enterprisedb.com>
` Re: Postmaster crashes on SIGHUP when oauth_validator_libraries holds only whitespace
2026-09-16 22:26 UTC Daniel Gustafsson <daniel@yesql.se>
` Re: Postmaster crashes on SIGHUP when oauth_validator_libraries holds only whitespace
2026-09-17 22:24 UTC Daniel Gustafsson <daniel@yesql.se>
` Re: Postmaster crashes on SIGHUP when oauth_validator_libraries holds only whitespace
2026-09-30 18:00 UTC Alexander Lakhin <exclusion@gmail.com>
` Re: Postmaster crashes on SIGHUP when oauth_validator_libraries holds only whitespace
2026-09-30 18:20 UTC Jacob Champion <jacob.champion@enterprisedb.com>
[12+ messages in thread]
Recovery does not honor io_combine_limit, causing IOPS saturation
2026-07-26 05:47 UTC Mats Kindahl <mats.kindahl@gmail.com>
` Re: Recovery does not honor io_combine_limit, causing IOPS saturation
2026-09-14 11:29 UTC Markos Fountoulakis <markos@planetscale.com>
` Re: Recovery does not honor io_combine_limit, causing IOPS saturation
2026-09-14 18:44 UTC Andrey Borodin <x4mmm@yandex-team.ru>
` Re: Recovery does not honor io_combine_limit, causing IOPS saturation
2026-09-30 17:46 UTC Mats Kindahl <mats.kindahl@gmail.com>
[4+ messages in thread]
[next (older)]
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox