pgsql-hackers  

Messages by Thread

• • Re: [PATCH] Add pg_get_event_trigger_ddl() function Ian Lawrence Barwick
  • Re: [PATCH] Add pg_get_event_trigger_ddl() function solai v
• [PATCH] Ignore duplicate IS [NOT] NULL clauses in clauselist_selectivity() Logan Saso
• Re: ci: namespace ccache by PostgreSQL major version Andres Freund
  • Re: ci: namespace ccache by PostgreSQL major version Jelte Fennema-Nio
  • Re: ci: namespace ccache by PostgreSQL major version Nazir Bilal Yavuz
  • Re: ci: namespace ccache by PostgreSQL major version Jelte Fennema-Nio
  • Re: ci: namespace ccache by PostgreSQL major version Andres Freund
  • Re: ci: namespace ccache by PostgreSQL major version Jacob Champion
  • Re: ci: namespace ccache by PostgreSQL major version Andres Freund
  • Re: ci: namespace ccache by PostgreSQL major version Jacob Champion
  • Re: ci: namespace ccache by PostgreSQL major version Jelte Fennema-Nio
  • Re: ci: namespace ccache by PostgreSQL major version Jelte Fennema-Nio
  • Re: ci: namespace ccache by PostgreSQL major version Jelte Fennema-Nio
  • Re: ci: namespace ccache by PostgreSQL major version Nazir Bilal Yavuz
  • Re: ci: namespace ccache by PostgreSQL major version Jelte Fennema-Nio
  • Re: ci: namespace ccache by PostgreSQL major version Nazir Bilal Yavuz
  • Re: ci: namespace ccache by PostgreSQL major version Andres Freund
• Re: Report index currently being vacuumed in pg_stat_progress_vacuum Sami Imseih
  • Re: Report index currently being vacuumed in pg_stat_progress_vacuum Sami Imseih
  • Re: Report index currently being vacuumed in pg_stat_progress_vacuum Bharath Rupireddy
  • Re: Report index currently being vacuumed in pg_stat_progress_vacuum Sami Imseih
  • Re: Report index currently being vacuumed in pg_stat_progress_vacuum Bharath Rupireddy
  • Re: Report index currently being vacuumed in pg_stat_progress_vacuum Sami Imseih
  • Re: Report index currently being vacuumed in pg_stat_progress_vacuum Michael Paquier
  • Re: Report index currently being vacuumed in pg_stat_progress_vacuum Michael Paquier
  • Re: Report index currently being vacuumed in pg_stat_progress_vacuum Sami Imseih
  • Re: Report index currently being vacuumed in pg_stat_progress_vacuum Sami Imseih
• TDE: Benchmarking WAL encryption approaches Zsolt Parragi
  • RE: TDE: Benchmarking WAL encryption approaches Hayato Kuroda (Fujitsu)
  • Re: TDE: Benchmarking WAL encryption approaches Zsolt Parragi
• Re: WAL compression setting after PostgreSQL LZ4 default change Tomas Vondra
  • Re: WAL compression setting after PostgreSQL LZ4 default change Andres Freund
  • Re: WAL compression setting after PostgreSQL LZ4 default change Laurenz Albe
  • Re: WAL compression setting after PostgreSQL LZ4 default change wenhui qiu
  • Re: WAL compression setting after PostgreSQL LZ4 default change Christoph Berg
  • Re: WAL compression setting after PostgreSQL LZ4 default change Tomas Vondra
  • Re: WAL compression setting after PostgreSQL LZ4 default change Christoph Berg
  • Re: WAL compression setting after PostgreSQL LZ4 default change Andrey Borodin
  • Re: WAL compression setting after PostgreSQL LZ4 default change Christoph Berg
  • Re: WAL compression setting after PostgreSQL LZ4 default change Tomas Vondra
  • Re: WAL compression setting after PostgreSQL LZ4 default change Christoph Berg
  • Re: WAL compression setting after PostgreSQL LZ4 default change Japin Li
  • Re: WAL compression setting after PostgreSQL LZ4 default change Michael Paquier
  • Re: WAL compression setting after PostgreSQL LZ4 default change Andreas Karlsson
  • Re: WAL compression setting after PostgreSQL LZ4 default change Hannu Krosing
  • Re: WAL compression setting after PostgreSQL LZ4 default change Tomas Vondra
  • Re: WAL compression setting after PostgreSQL LZ4 default change Hannu Krosing
  • Re: WAL compression setting after PostgreSQL LZ4 default change Tomas Vondra
  • Re: WAL compression setting after PostgreSQL LZ4 default change Hannu Krosing
  • Re: WAL compression setting after PostgreSQL LZ4 default change Hannu Krosing
  • Re: WAL compression setting after PostgreSQL LZ4 default change Ken Marshall
  • Re: WAL compression setting after PostgreSQL LZ4 default change Tomas Vondra
  • Re: WAL compression setting after PostgreSQL LZ4 default change wenhui qiu
  • Re: WAL compression setting after PostgreSQL LZ4 default change Tomas Vondra
  • Re: WAL compression setting after PostgreSQL LZ4 default change Andrey Borodin
  • Re: WAL compression setting after PostgreSQL LZ4 default change Tomas Vondra
  • Re: WAL compression setting after PostgreSQL LZ4 default change Tomas Vondra
  • Re: WAL compression setting after PostgreSQL LZ4 default change Christoph Berg
  • Re: WAL compression setting after PostgreSQL LZ4 default change Daniel Gustafsson
  • Re: WAL compression setting after PostgreSQL LZ4 default change Jelte Fennema-Nio
  • Re: WAL compression setting after PostgreSQL LZ4 default change Michael Paquier
  • Re: WAL compression setting after PostgreSQL LZ4 default change Tomas Vondra
  • Re: WAL compression setting after PostgreSQL LZ4 default change Christoph Berg
  • Re: WAL compression setting after PostgreSQL LZ4 default change Daniel Gustafsson
  • Re: WAL compression setting after PostgreSQL LZ4 default change Tomas Vondra
  • Re: WAL compression setting after PostgreSQL LZ4 default change wenhui qiu
  • Re: WAL compression setting after PostgreSQL LZ4 default change Tomas Vondra
  • Re: WAL compression setting after PostgreSQL LZ4 default change Michael Paquier
• Re: Show hashed SAOP decision in EXPLAIN Ayush Tiwari
• Re: Allow table AMs to define their own reloptions Rafia Sabih
  • Re: Allow table AMs to define their own reloptions Andrew Dunstan
  • Re: Allow table AMs to define their own reloptions Rafia Sabih
  • Re: Allow table AMs to define their own reloptions Andrew Dunstan
  • Re: Allow table AMs to define their own reloptions Zsolt Parragi
• Re: encode/decode support for base64url Daniel Gustafsson
  • Re: encode/decode support for base64url David E. Wheeler
  • Re: encode/decode support for base64url Daniel Gustafsson
• Re: Type assertions without GCC builtins Peter Eisentraut
  • Re: Type assertions without GCC builtins Tom Lane
• Re: ri_Fast* crash w/ nullable UNIQUE constraint Amit Langote
  • Re: ri_Fast* crash w/ nullable UNIQUE constraint Noah Misch
  • Re: ri_Fast* crash w/ nullable UNIQUE constraint Amit Langote
  • Re: ri_Fast* crash w/ nullable UNIQUE constraint Ayush Tiwari
  • Re: ri_Fast* crash w/ nullable UNIQUE constraint Amit Langote
  • Re: ri_Fast* crash w/ nullable UNIQUE constraint Ayush Tiwari
  • Re: ri_Fast* crash w/ nullable UNIQUE constraint Amit Langote
  • Re: ri_Fast* crash w/ nullable UNIQUE constraint Amit Langote
  • Re: ri_Fast* crash w/ nullable UNIQUE constraint Amit Langote
  • Re: ri_Fast* crash w/ nullable UNIQUE constraint Noah Misch
• Re: clean up size_t/ssize_t use with POSIX file system APIs Peter Eisentraut
• [PATCH] Do not flush BufFile for regular temp files Sergey Soloviev
  • Re: [PATCH] Do not flush BufFile for regular temp files Pierre Forstmann
• Re: Is there value in having optimizer stats for joins/foreignkeys? Ilia Evdokimov
  • Re: Is there value in having optimizer stats for joins/foreignkeys? Corey Huinker
  • Re: Is there value in having optimizer stats for joins/foreignkeys? Tomas Vondra
  • Re: Is there value in having optimizer stats for joins/foreignkeys? Tomas Vondra
  • Re: Is there value in having optimizer stats for joins/foreignkeys? Tomas Vondra
  • Re: Is there value in having optimizer stats for joins/foreignkeys? Chengpeng Yan
• [PATCH] Rewrite undirected edge patterns in GRAPH_TABLE using UNION ALL ayoub . kazar
  • Re: [PATCH] Rewrite undirected edge patterns in GRAPH_TABLE using UNION ALL Ashutosh Bapat
  • Re: [PATCH] Rewrite undirected edge patterns in GRAPH_TABLE using UNION ALL ayoub . kazar
  • Re: [PATCH] Rewrite undirected edge patterns in GRAPH_TABLE using UNION ALL ayoub . kazar
  • Re: [PATCH] Rewrite undirected edge patterns in GRAPH_TABLE using UNION ALL ayoub . kazar
  • Re: [PATCH] Rewrite undirected edge patterns in GRAPH_TABLE using UNION ALL ayoub . kazar
  • Re: [PATCH] Rewrite undirected edge patterns in GRAPH_TABLE using UNION ALL Ashutosh Bapat
  • Re: [PATCH] Rewrite undirected edge patterns in GRAPH_TABLE using UNION ALL Ayoub Kazar
  • Re: [PATCH] Rewrite undirected edge patterns in GRAPH_TABLE using UNION ALL Ashutosh Bapat
• Re: using index to speedup add not null constraints to a table jian he
• Re: [BUG] Take a long time to reach consistent after pg_rewind solai v
• Re: Bypassing cursors in postgres_fdw to enable parallel plans Yilin Zhang
  • Re: Bypassing cursors in postgres_fdw to enable parallel plans Rafia Sabih
  • Re: Bypassing cursors in postgres_fdw to enable parallel plans Robert Haas
  • Re: Bypassing cursors in postgres_fdw to enable parallel plans Rafia Sabih
  • Re: Bypassing cursors in postgres_fdw to enable parallel plans Robert Haas
  • Re: Bypassing cursors in postgres_fdw to enable parallel plans Rafia Sabih
  • Re: Bypassing cursors in postgres_fdw to enable parallel plans Robert Haas
  • Re: Bypassing cursors in postgres_fdw to enable parallel plans Rafia Sabih
  • Re: Bypassing cursors in postgres_fdw to enable parallel plans Robert Haas
  • Re: Bypassing cursors in postgres_fdw to enable parallel plans Robert Haas
• Fix RETURNING side effects for FOR PORTION OF leftover rows Chao Li
  • Re: Fix RETURNING side effects for FOR PORTION OF leftover rows Dean Rasheed
  • Re: Fix RETURNING side effects for FOR PORTION OF leftover rows Chao Li
  • Re: Fix RETURNING side effects for FOR PORTION OF leftover rows Paul A Jungwirth
  • Re: Fix RETURNING side effects for FOR PORTION OF leftover rows Dean Rasheed
  • Re: Fix RETURNING side effects for FOR PORTION OF leftover rows Paul A Jungwirth
  • Re: Fix RETURNING side effects for FOR PORTION OF leftover rows Chao Li
  • Re: Fix RETURNING side effects for FOR PORTION OF leftover rows Dean Rasheed
  • Re: Fix RETURNING side effects for FOR PORTION OF leftover rows Chao Li
• Re: Improve pg_stat_statements scalability Kyotaro Horiguchi
  • Re: Improve pg_stat_statements scalability Michael Paquier
  • Re: Improve pg_stat_statements scalability Sami Imseih
  • Re: Improve pg_stat_statements scalability Sami Imseih
  • Re: Improve pg_stat_statements scalability Kyotaro Horiguchi
• Re: tablecmds: fix bug where index rebuild loses replica identity on partitions Chao Li
  • Re: tablecmds: fix bug where index rebuild loses replica identity on partitions Alberto Piai
  • Re: tablecmds: fix bug where index rebuild loses replica identity on partitions Sami Imseih
  • Re: tablecmds: fix bug where index rebuild loses replica identity on partitions Sami Imseih
  • Re: tablecmds: fix bug where index rebuild loses replica identity on partitions Alberto Piai
  • Re: tablecmds: fix bug where index rebuild loses replica identity on partitions Chao Li
  • Re: tablecmds: fix bug where index rebuild loses replica identity on partitions Alberto Piai
  • Re: tablecmds: fix bug where index rebuild loses replica identity on partitions Chao Li
  • Re: tablecmds: fix bug where index rebuild loses replica identity on partitions Sami Imseih
  • Re: tablecmds: fix bug where index rebuild loses replica identity on partitions Chao Li
  • Re: tablecmds: fix bug where index rebuild loses replica identity on partitions Sami Imseih
  • Re: tablecmds: fix bug where index rebuild loses replica identity on partitions Chao Li
  • Re: tablecmds: fix bug where index rebuild loses replica identity on partitions Alberto Piai
  • Re: tablecmds: fix bug where index rebuild loses replica identity on partitions Chao Li
• Follow-up fixes for online wal_level change Masahiko Sawada
  • Re: Follow-up fixes for online wal_level change Guoqing Yang
  • RE: Follow-up fixes for online wal_level change Hayato Kuroda (Fujitsu)
  • Re: Follow-up fixes for online wal_level change Masahiko Sawada
  • Re: Follow-up fixes for online wal_level change Fujii Masao
  • RE: Follow-up fixes for online wal_level change Hayato Kuroda (Fujitsu)
  • Re: Follow-up fixes for online wal_level change Masahiko Sawada
  • Re: Follow-up fixes for online wal_level change Masahiko Sawada
  • Re: Follow-up fixes for online wal_level change Masahiko Sawada
  • Re: Follow-up fixes for online wal_level change Masahiko Sawada
  • Re: Follow-up fixes for online wal_level change Masahiko Sawada
• pgstat: add pgstat_prep_pending() for entry ref pending setup Sami Imseih
  • Re: pgstat: add pgstat_prep_pending() for entry ref pending setup Michael Paquier
  • Re: pgstat: add pgstat_prep_pending() for entry ref pending setup Sami Imseih
  • Re: pgstat: add pgstat_prep_pending() for entry ref pending setup Michael Paquier
  • Re: pgstat: add pgstat_prep_pending() for entry ref pending setup Kyotaro Horiguchi
  • Re: pgstat: add pgstat_prep_pending() for entry ref pending setup Michael Paquier
  • Re: pgstat: add pgstat_prep_pending() for entry ref pending setup Sami Imseih
  • Re: pgstat: add pgstat_prep_pending() for entry ref pending setup Michael Paquier
  • Re: pgstat: add pgstat_prep_pending() for entry ref pending setup Michael Paquier
• Re: VS 2026 support on old branches Andrew Dunstan
  • Re: VS 2026 support on old branches Michael Paquier
  • Re: VS 2026 support on old branches Andrew Dunstan
• Re: Remove getpgusername() surya poondla
  • Re: Remove getpgusername() Michael Paquier
  • Re: Remove getpgusername() Michael Paquier
  • Re: Remove getpgusername() Ian Lawrence Barwick
  • Re: Remove getpgusername() Ian Lawrence Barwick
• Re: Fix RLS checks for UPDATE/DELETE FOR PORTION OF leftover rows Dean Rasheed
  • Re: Fix RLS checks for UPDATE/DELETE FOR PORTION OF leftover rows Paul A Jungwirth
  • Re: Fix RLS checks for UPDATE/DELETE FOR PORTION OF leftover rows Dean Rasheed
  • Re: Fix RLS checks for UPDATE/DELETE FOR PORTION OF leftover rows Paul A Jungwirth
  • Re: Fix RLS checks for UPDATE/DELETE FOR PORTION OF leftover rows Chao Li
  • Re: Fix RLS checks for UPDATE/DELETE FOR PORTION OF leftover rows Paul A Jungwirth
  • Re: Fix RLS checks for UPDATE/DELETE FOR PORTION OF leftover rows Peter Eisentraut
  • Re: Fix RLS checks for UPDATE/DELETE FOR PORTION OF leftover rows Chao Li
• Re: [DESIGN] Soft DROP TABLE, recoverable drops for PostgreSQL surya poondla
  • Re: [DESIGN] Soft DROP TABLE, recoverable drops for PostgreSQL Zsolt Parragi
  • Re: [DESIGN] Soft DROP TABLE, recoverable drops for PostgreSQL surya poondla
  • Re: [DESIGN] Soft DROP TABLE, recoverable drops for PostgreSQL Andreas Karlsson
  • Re: [DESIGN] Soft DROP TABLE, recoverable drops for PostgreSQL Amit Kapila
  • Re: [DESIGN] Soft DROP TABLE, recoverable drops for PostgreSQL Álvaro Herrera
  • Re: [DESIGN] Soft DROP TABLE, recoverable drops for PostgreSQL Amit Kapila
  • Re: [DESIGN] Soft DROP TABLE, recoverable drops for PostgreSQL surya poondla
  • Re: [DESIGN] Soft DROP TABLE, recoverable drops for PostgreSQL Amit Kapila
• [PATCH] pgbench: fix incorrect long option name in error message Semih Doğan
  • Re: [PATCH] pgbench: fix incorrect long option name in error message Daniel Gustafsson
• pgstat: allow a stats kind to use its own dedicated dsa/dshash Sami Imseih
  • Re: pgstat: allow a stats kind to use its own dedicated dsa/dshash Bertrand Drouvot
• Re: Unexpected changes of CurrentResourceOwner and CurrentMemoryContext Álvaro Herrera
  • Re: Unexpected changes of CurrentResourceOwner and CurrentMemoryContext Antonin Houska
• [PATCH] The heap_getsysattr function deletes unused parameters lei yang

• Earlier messages
• Later messages