pgsql-hackers  

Messages by Thread

• • Re: Handle concurrent drop when doing whole database vacuum Kyotaro Horiguchi
  • Re: Handle concurrent drop when doing whole database vacuum cca5507
  • Re: Handle concurrent drop when doing whole database vacuum Kyotaro Horiguchi
  • Re: Handle concurrent drop when doing whole database vacuum surya poondla
  • Re: Handle concurrent drop when doing whole database vacuum Michael Paquier
  • Re: Handle concurrent drop when doing whole database vacuum Bharath Rupireddy
  • Re: Handle concurrent drop when doing whole database vacuum Michael Paquier
  • Re: Handle concurrent drop when doing whole database vacuum cca5507
  • Re: Handle concurrent drop when doing whole database vacuum Michael Paquier
  • Re: Handle concurrent drop when doing whole database vacuum Nathan Bossart
  • Re: Handle concurrent drop when doing whole database vacuum Michael Paquier
  • Re: Handle concurrent drop when doing whole database vacuum Nathan Bossart
  • Re: Handle concurrent drop when doing whole database vacuum Bharath Rupireddy
  • Re: Handle concurrent drop when doing whole database vacuum Nathan Bossart
  • Re: Handle concurrent drop when doing whole database vacuum surya poondla
• Little checksum worker cleanups Heikki Linnakangas
  • Re: Little checksum worker cleanups Daniel Gustafsson
  • Re: Little checksum worker cleanups Daniel Gustafsson
  • Re: Little checksum worker cleanups Heikki Linnakangas
• Re: [PATCH] Improving index selection for logical replication apply with replica identity full Bharath Rupireddy
  • Re: [PATCH] Improving index selection for logical replication apply with replica identity full Ethan Mertz
  • Re: [PATCH] Improving index selection for logical replication apply with replica identity full Bharath Rupireddy
  • Re: [PATCH] Improving index selection for logical replication apply with replica identity full Ethan Mertz
• Re: Problems with get_actual_variable_range's VISITED_PAGES_LIMIT Peter Geoghegan
  • Re: Problems with get_actual_variable_range's VISITED_PAGES_LIMIT Jakub Wartak
• Re: Additional message in pg_terminate_backend Paul A Jungwirth
  • Re: Additional message in pg_terminate_backend warda Bibi
• Add MIN/MAX aggregate support for uuid Tristan Partin
  • Re: Add MIN/MAX aggregate support for uuid Tristan Partin
  • Re: Add MIN/MAX aggregate support for uuid Bharath Rupireddy
  • Re: Add MIN/MAX aggregate support for uuid Tristan Partin
  • Re: Add MIN/MAX aggregate support for uuid Masahiko Sawada
  • Re: Add MIN/MAX aggregate support for uuid Tristan Partin
  • Re: Add MIN/MAX aggregate support for uuid Bharath Rupireddy
  • Re: Add MIN/MAX aggregate support for uuid Tristan Partin
  • Re: Add MIN/MAX aggregate support for uuid Zsolt Parragi
  • Re: Add MIN/MAX aggregate support for uuid Tristan Partin
  • Re: Add MIN/MAX aggregate support for uuid Masahiko Sawada
  • Re: Add MIN/MAX aggregate support for uuid Masahiko Sawada
• Re: 048_vacuum_horizon_floor.pl hangs due to wakeup lost inside LockBufferForCleanup Xuneng Zhou
  • Re: 048_vacuum_horizon_floor.pl hangs due to wakeup lost inside LockBufferForCleanup Fujii Masao
  • Re: 048_vacuum_horizon_floor.pl hangs due to wakeup lost inside LockBufferForCleanup Xuneng Zhou
  • Re: 048_vacuum_horizon_floor.pl hangs due to wakeup lost inside LockBufferForCleanup Fujii Masao
  • Re: 048_vacuum_horizon_floor.pl hangs due to wakeup lost inside LockBufferForCleanup Xuneng Zhou
  • Re: 048_vacuum_horizon_floor.pl hangs due to wakeup lost inside LockBufferForCleanup Xuneng Zhou
• Re: [PATCH] Warn when io_min_workers exceeds io_max_workers Baji Shaik
  • Re: [PATCH] Warn when io_min_workers exceeds io_max_workers Michael Paquier
  • Re: [PATCH] Warn when io_min_workers exceeds io_max_workers Michael Paquier
• Re: [GSoC 2026] - B-tree Index Bloat Reduction - Approach & Questions Kirk Wolak
  • Re: [GSoC 2026] - B-tree Index Bloat Reduction - Approach & Questions Peter Geoghegan
  • Re: [GSoC 2026] - B-tree Index Bloat Reduction - Approach & Questions Matthias van de Meent
  • Re: [GSoC 2026] - B-tree Index Bloat Reduction - Approach & Questions Peter Geoghegan
  • Re: [GSoC 2026] - B-tree Index Bloat Reduction - Approach & Questions Matthias van de Meent
  • Re: [GSoC 2026] - B-tree Index Bloat Reduction - Approach & Questions Peter Geoghegan
  • Re: [GSoC 2026] - B-tree Index Bloat Reduction - Approach & Questions Kirk Wolak
  • Re: [GSoC 2026] - B-tree Index Bloat Reduction - Approach & Questions Robert Haas
  • Re: [GSoC 2026] - B-tree Index Bloat Reduction - Approach & Questions Peter Geoghegan
  • Re: [GSoC 2026] - B-tree Index Bloat Reduction - Approach & Questions Salma El-Sayed
  • Re: [GSoC 2026] - B-tree Index Bloat Reduction - Approach & Questions Matthias van de Meent
  • Re: [GSoC 2026] - B-tree Index Bloat Reduction - Approach & Questions Salma El-Sayed
  • Re: [GSoC 2026] - B-tree Index Bloat Reduction - Approach & Questions Kirk Wolak
  • Re: [GSoC 2026] - B-tree Index Bloat Reduction - Approach & Questions Andrey Borodin
  • Re: [GSoC 2026] - B-tree Index Bloat Reduction - Approach & Questions Matthias van de Meent
  • Re: [GSoC 2026] - B-tree Index Bloat Reduction - Approach & Questions Kirk Wolak
  • Re: [GSoC 2026] - B-tree Index Bloat Reduction - Approach & Questions Salma El-Sayed
• libpq: decouple the .pgpass lookup port from the connection port Diego
  • [PATCH] - Re: libpq: decouple the .pgpass lookup port from the connection port Diego
  • Re: [PATCH] - Re: libpq: decouple the .pgpass lookup port from the connection port Diego
  • Re: libpq: decouple the .pgpass lookup port from the connection port Christoph Berg
  • Re: libpq: decouple the .pgpass lookup port from the connection port Diego
• Re: Fix HAVING-to-WHERE pushdown with mismatched operator families Zsolt Parragi
  • Re: Fix HAVING-to-WHERE pushdown with mismatched operator families Richard Guo
  • Re: Fix HAVING-to-WHERE pushdown with mismatched operator families Tender Wang
  • Re: Fix HAVING-to-WHERE pushdown with mismatched operator families Tender Wang
  • Re: Fix HAVING-to-WHERE pushdown with mismatched operator families Richard Guo
  • Re: Fix HAVING-to-WHERE pushdown with mismatched operator families Tender Wang
  • Re: Fix HAVING-to-WHERE pushdown with mismatched operator families Richard Guo
  • Re: Fix HAVING-to-WHERE pushdown with mismatched operator families Tender Wang
  • Re: Fix HAVING-to-WHERE pushdown with mismatched operator families Richard Guo
  • Re: Fix HAVING-to-WHERE pushdown with mismatched operator families Fujii Masao
  • Re: Fix HAVING-to-WHERE pushdown with mismatched operator families Richard Guo
  • Re: Fix HAVING-to-WHERE pushdown with mismatched operator families Chengpeng Yan
• Re: More jsonpath methods: translate, split, join Corey Huinker
  • Re: More jsonpath methods: translate, split, join Florents Tselai
  • Re: More jsonpath methods: translate, split, join Florents Tselai
  • Re: More jsonpath methods: translate, split, join Corey Huinker
  • Re: More jsonpath methods: translate, split, join Florents Tselai
  • Re: More jsonpath methods: translate, split, join Zsolt Parragi
  • Re: More jsonpath methods: translate, split, join Florents Tselai
  • Re: More jsonpath methods: translate, split, join Florents Tselai
• Re: File locks for data directory lockfile in the context of Linux namespaces Dmitry Dolgov
  • Re: File locks for data directory lockfile in the context of Linux namespaces Ilmar Yunusov
  • Re: File locks for data directory lockfile in the context of Linux namespaces Dmitry Dolgov
  • Re: File locks for data directory lockfile in the context of Linux namespaces Zsolt Parragi
  • Re: File locks for data directory lockfile in the context of Linux namespaces Dmitry Dolgov
• Re: Row pattern recognition Henson Choi
  • Re: Row pattern recognition jian he
  • Re: Row pattern recognition jian he
  • Re: Row pattern recognition Henson Choi
  • Re: Row pattern recognition Henson Choi
  • Re: Row pattern recognition Henson Choi
  • Re: Row pattern recognition Tatsuo Ishii
  • Re: Row pattern recognition Henson Choi
  • Re: Row pattern recognition Henson Choi
  • Re: Row pattern recognition Tatsuo Ishii
  • Re: Row pattern recognition Henson Choi
  • Re: Row pattern recognition Tatsuo Ishii
  • Re: Row pattern recognition Henson Choi
  • Re: Row pattern recognition jian he
  • Re: Row pattern recognition Henson Choi
  • Re: Row pattern recognition Tatsuo Ishii
  • Re: Row pattern recognition Henson Choi
  • Re: Row pattern recognition Tatsuo Ishii
  • Re: Row pattern recognition jian he
  • Re: Row pattern recognition jian he
  • Re: Row pattern recognition jian he
  • Re: Row pattern recognition Tatsuo Ishii
  • Re: Row pattern recognition Henson Choi
  • Re: Row pattern recognition jian he
  • Re: Row pattern recognition Tatsuo Ishii
  • Re: Row pattern recognition Henson Choi
  • Re: Row pattern recognition Henson Choi
  • Re: Row pattern recognition Tatsuo Ishii
  • Re: Row pattern recognition Henson Choi
  • Re: Row pattern recognition Henson Choi
  • Re: Row pattern recognition Henson Choi
  • Re: Row pattern recognition Henson Choi
  • Re: Row pattern recognition Tatsuo Ishii
  • Re: Row pattern recognition jian he
  • Re: Row pattern recognition jian he
  • Re: Row pattern recognition Henson Choi
  • Re: Row pattern recognition Henson Choi
  • Re: Row pattern recognition Tatsuo Ishii
  • Re: Row pattern recognition Henson Choi
  • Re: Row pattern recognition 신성준
  • Re: Row pattern recognition Tatsuo Ishii
  • Re: Row pattern recognition 신성준
  • Re: Row pattern recognition Tatsuo Ishii
  • Re: Row pattern recognition Henson Choi
  • Re: Row pattern recognition Tatsuo Ishii
  • Re: Row pattern recognition Henson Choi
  • Re: Row pattern recognition Tatsuo Ishii
  • Re: Row pattern recognition Henson Choi
  • Re: Row pattern recognition Tatsuo Ishii
  • Re: Row pattern recognition Tatsuo Ishii
• Re: for loop variable fixes Tom Lane
  • Re: for loop variable fixes Peter Eisentraut
  • Re: for loop variable fixes Peter Eisentraut
• Re: The PostgreSQL C Dialect Tom Lane
  • Re: The PostgreSQL C Dialect Christophe Pettus
  • Re: The PostgreSQL C Dialect Peter Smith
  • Re: The PostgreSQL C Dialect Christophe Pettus
  • Re: The PostgreSQL C Dialect Christophe Pettus
  • Re: The PostgreSQL C Dialect Jelte Fennema-Nio
  • Re: The PostgreSQL C Dialect Christophe Pettus
  • Re: The PostgreSQL C Dialect jian he
  • Re: The PostgreSQL C Dialect jian he
  • Re: The PostgreSQL C Dialect Corey Huinker
• Re: Logging parallel worker draught Andrei Lepikhov
  • Re: Logging parallel worker draught Benoit Lobréau
  • Re: Logging parallel worker draught Andrei Lepikhov
• Re: Hash-based MCV matching for large IN-lists Ilia Evdokimov
• Re: [PATCH] Preserve replication origin OIDs in pg_upgrade Ajin Cherian
  • Re: [PATCH] Preserve replication origin OIDs in pg_upgrade Rui Zhao
  • Re: [PATCH] Preserve replication origin OIDs in pg_upgrade shveta malik
  • Re: [PATCH] Preserve replication origin OIDs in pg_upgrade shveta malik
  • Re: [PATCH] Preserve replication origin OIDs in pg_upgrade Shlok Kyal
  • Re: [PATCH] Preserve replication origin OIDs in pg_upgrade Zsolt Parragi
  • Re: [PATCH] Preserve replication origin OIDs in pg_upgrade Ajin Cherian
  • Re: [PATCH] Preserve replication origin OIDs in pg_upgrade Rui Zhao
  • Re: [PATCH] Preserve replication origin OIDs in pg_upgrade shveta malik
  • Re: [PATCH] Preserve replication origin OIDs in pg_upgrade shveta malik
  • Re: [PATCH] Preserve replication origin OIDs in pg_upgrade Shlok Kyal
  • Re: [PATCH] Preserve replication origin OIDs in pg_upgrade Rui Zhao
  • Re: [PATCH] Preserve replication origin OIDs in pg_upgrade shveta malik
  • Re: [PATCH] Preserve replication origin OIDs in pg_upgrade shveta malik
  • RE: [PATCH] Preserve replication origin OIDs in pg_upgrade Hayato Kuroda (Fujitsu)
  • Re: [PATCH] Preserve replication origin OIDs in pg_upgrade shveta malik
  • Re: [PATCH] Preserve replication origin OIDs in pg_upgrade Amit Kapila
  • RE: [PATCH] Preserve replication origin OIDs in pg_upgrade Hayato Kuroda (Fujitsu)
  • Re: [PATCH] Preserve replication origin OIDs in pg_upgrade Amit Kapila
  • Re: [PATCH] Preserve replication origin OIDs in pg_upgrade shveta malik
  • Re: [PATCH] Preserve replication origin OIDs in pg_upgrade Ajin Cherian
  • Re: [PATCH] Preserve replication origin OIDs in pg_upgrade shveta malik
  • Re: [PATCH] Preserve replication origin OIDs in pg_upgrade Shlok Kyal
  • Re: [PATCH] Preserve replication origin OIDs in pg_upgrade Ajin Cherian
  • Re: [PATCH] Preserve replication origin OIDs in pg_upgrade shveta malik
  • Re: [PATCH] Preserve replication origin OIDs in pg_upgrade Ajin Cherian
  • Re: [PATCH] Preserve replication origin OIDs in pg_upgrade Shlok Kyal
  • Re: [PATCH] Preserve replication origin OIDs in pg_upgrade Shlok Kyal
  • Re: [PATCH] Preserve replication origin OIDs in pg_upgrade Ajin Cherian
  • Re: [PATCH] Preserve replication origin OIDs in pg_upgrade shveta malik
  • Re: [PATCH] Preserve replication origin OIDs in pg_upgrade Rui Zhao
  • Re: [PATCH] Preserve replication origin OIDs in pg_upgrade shveta malik
  • Re: [PATCH] Preserve replication origin OIDs in pg_upgrade Ajin Cherian
  • Re: [PATCH] Preserve replication origin OIDs in pg_upgrade Amit Kapila
• Re: use of SPI by postgresImportForeignStatistics jian he
  • Re: use of SPI by postgresImportForeignStatistics Corey Huinker
  • Re: use of SPI by postgresImportForeignStatistics Robert Haas
  • Re: use of SPI by postgresImportForeignStatistics Corey Huinker

• Earlier messages
• Later messages