pgsql-hackers  

Messages by Thread

• • Re: Revisiting {CREATE INDEX, REINDEX} CONCURRENTLY improvements Matthias van de Meent
  • Re: Revisiting {CREATE INDEX, REINDEX} CONCURRENTLY improvements Mihail Nikalayeu
  • Re: Revisiting {CREATE INDEX, REINDEX} CONCURRENTLY improvements Matthias van de Meent
  • Re: Revisiting {CREATE INDEX, REINDEX} CONCURRENTLY improvements Hannu Krosing
  • Re: Revisiting {CREATE INDEX, REINDEX} CONCURRENTLY improvements Hannu Krosing
  • Re: Revisiting {CREATE INDEX, REINDEX} CONCURRENTLY improvements Mihail Nikalayeu
  • Re: Revisiting {CREATE INDEX, REINDEX} CONCURRENTLY improvements Antonin Houska
  • Re: Revisiting {CREATE INDEX, REINDEX} CONCURRENTLY improvements Mihail Nikalayeu
  • Re: Revisiting {CREATE INDEX, REINDEX} CONCURRENTLY improvements Antonin Houska
  • Re: Revisiting {CREATE INDEX, REINDEX} CONCURRENTLY improvements Mihail Nikalayeu
  • Re: Revisiting {CREATE INDEX, REINDEX} CONCURRENTLY improvements Matthias van de Meent
  • Re: Revisiting {CREATE INDEX, REINDEX} CONCURRENTLY improvements Matthias van de Meent
  • Re: Revisiting {CREATE INDEX, REINDEX} CONCURRENTLY improvements Hannu Krosing
  • Re: Revisiting {CREATE INDEX, REINDEX} CONCURRENTLY improvements Mihail Nikalayeu
  • Re: Revisiting {CREATE INDEX, REINDEX} CONCURRENTLY improvements Hannu Krosing
  • Re: Revisiting {CREATE INDEX, REINDEX} CONCURRENTLY improvements Matthias van de Meent
  • Re: Revisiting {CREATE INDEX, REINDEX} CONCURRENTLY improvements Antonin Houska
  • Re: Revisiting {CREATE INDEX, REINDEX} CONCURRENTLY improvements Matthias van de Meent
  • Re: Revisiting {CREATE INDEX, REINDEX} CONCURRENTLY improvements Antonin Houska
  • Re: Revisiting {CREATE INDEX, REINDEX} CONCURRENTLY improvements Matthias van de Meent
  • Re: Revisiting {CREATE INDEX, REINDEX} CONCURRENTLY improvements Antonin Houska
  • Re: Revisiting {CREATE INDEX, REINDEX} CONCURRENTLY improvements Hannu Krosing
• Using MyDatabaseId in SET_LOCKTAG_APPLY_TRANSACTION Maxim Orlov
  • Re: Using MyDatabaseId in SET_LOCKTAG_APPLY_TRANSACTION Heikki Linnakangas
  • Re: Using MyDatabaseId in SET_LOCKTAG_APPLY_TRANSACTION Maxim Orlov
  • RE: Using MyDatabaseId in SET_LOCKTAG_APPLY_TRANSACTION Hayato Kuroda (Fujitsu)
  • Re: Using MyDatabaseId in SET_LOCKTAG_APPLY_TRANSACTION Maxim Orlov
• weird ON CONFLICT clauses Álvaro Herrera
  • Re: weird ON CONFLICT clauses Peter Geoghegan
• Mention TABLEFUNC to make comment consistent with code Steve Lau
• [PATCH] Add `headerscheck` run_target to meson Miłosz Bieniek
  • Re: [PATCH] Add `headerscheck` run_target to meson Peter Eisentraut
  • Re: [PATCH] Add `headerscheck` run_target to meson Miłosz Bieniek
  • Re: [PATCH] Add `headerscheck` run_target to meson Nazir Bilal Yavuz
  • Re: [PATCH] Add `headerscheck` run_target to meson Nazir Bilal Yavuz
  • Re: [PATCH] Add `headerscheck` run_target to meson Miłosz Bieniek
  • Re: [PATCH] Add `headerscheck` run_target to meson Bilal Yavuz
• https://cfbot.cputube.org - certificate has expired Aleksander Alekseev
  • Re: https://cfbot.cputube.org - certificate has expired Nazir Bilal Yavuz
  • Re: https://cfbot.cputube.org - certificate has expired Aleksander Alekseev
  • Re: https://cfbot.cputube.org - certificate has expired Nazir Bilal Yavuz
  • Re: https://cfbot.cputube.org - certificate has expired Thomas Munro
  • Re: https://cfbot.cputube.org - certificate has expired Thomas Munro
• Remove unused function parameters, part 1: contrib Bertrand Drouvot
  • Re: Remove unused function parameters, part 1: contrib Kirill Reshke
  • Re: Remove unused function parameters, part 1: contrib Bertrand Drouvot
  • Re: Remove unused function parameters, part 1: contrib Jacob Champion
  • Re: Remove unused function parameters, part 1: contrib Nazir Bilal Yavuz
  • Re: Remove unused function parameters, part 1: contrib Bertrand Drouvot
• Re: pgsql: doc: Fix incorrect wording for --file in pg_dump Erik Rijkers
  • Re: pgsql: doc: Fix incorrect wording for --file in pg_dump Chao Li
  • Re: pgsql: doc: Fix incorrect wording for --file in pg_dump Michael Paquier
  • Re: pgsql: doc: Fix incorrect wording for --file in pg_dump Daniel Gustafsson
• Move WAL/RMGR sequence code into its own file and header Michael Paquier
  • Re: Move WAL/RMGR sequence code into its own file and header Heikki Linnakangas
  • Re: Move WAL/RMGR sequence code into its own file and header Michael Paquier
  • Re: Move WAL/RMGR sequence code into its own file and header Kirill Reshke
  • Re: Move WAL/RMGR sequence code into its own file and header Michael Paquier
  • Re: Move WAL/RMGR sequence code into its own file and header Michael Paquier
• Re: Consistently use palloc_object() and palloc_array() Chao Li
  • Re: Consistently use palloc_object() and palloc_array() David Geier
  • Re: Consistently use palloc_object() and palloc_array() Tom Lane
  • Re: Consistently use palloc_object() and palloc_array() David Geier
  • Re: Consistently use palloc_object() and palloc_array() Thomas Munro
  • Re: Consistently use palloc_object() and palloc_array() David Geier
  • Re: Consistently use palloc_object() and palloc_array() Michael Paquier
  • Re: Consistently use palloc_object() and palloc_array() Tom Lane
  • Re: Consistently use palloc_object() and palloc_array() Michael Paquier
  • Re: Consistently use palloc_object() and palloc_array() David Geier
  • Re: Consistently use palloc_object() and palloc_array() Tom Lane
  • Re: Consistently use palloc_object() and palloc_array() Michael Paquier
  • Re: Consistently use palloc_object() and palloc_array() Thomas Munro
  • Re: Consistently use palloc_object() and palloc_array() Michael Paquier
  • Re: Consistently use palloc_object() and palloc_array() David Geier
  • Re: Consistently use palloc_object() and palloc_array() Michael Paquier
  • Re: Consistently use palloc_object() and palloc_array() David Geier
  • Re: Consistently use palloc_object() and palloc_array() Thomas Munro
  • Re: Consistently use palloc_object() and palloc_array() Tom Lane
  • Re: Consistently use palloc_object() and palloc_array() Michael Paquier
  • Re: Consistently use palloc_object() and palloc_array() David Geier
  • Re: Consistently use palloc_object() and palloc_array() Peter Eisentraut
• show size of DSAs and dshash tables in pg_dsm_registry_allocations Nathan Bossart
  • Re: show size of DSAs and dshash tables in pg_dsm_registry_allocations Rahila Syed
  • Re: show size of DSAs and dshash tables in pg_dsm_registry_allocations Nathan Bossart
  • Re: show size of DSAs and dshash tables in pg_dsm_registry_allocations Robert Haas
  • Re: show size of DSAs and dshash tables in pg_dsm_registry_allocations Nathan Bossart
  • Re: show size of DSAs and dshash tables in pg_dsm_registry_allocations Chao Li
  • Re: show size of DSAs and dshash tables in pg_dsm_registry_allocations Nathan Bossart
  • Re: show size of DSAs and dshash tables in pg_dsm_registry_allocations Rahila Syed
  • Re: show size of DSAs and dshash tables in pg_dsm_registry_allocations Nathan Bossart
• Re: oid2name : add objects file path Guillaume Lelarge
  • Re: oid2name : add objects file path David Bidoc
  • Re: oid2name : add objects file path Michael Paquier
• Remove unused struct fields Bertrand Drouvot
  • Re: Remove unused struct fields Nathan Bossart
  • Re: Remove unused struct fields Nathan Bossart
• Re: [PATCH] Better Performance for PostgreSQL with large INSERTs Filip Janus
  • Re: [PATCH] Better Performance for PostgreSQL with large INSERTs Philipp Marek
• macOS - Sequoia CI task is stuck on the Postgres Github CI Nazir Bilal Yavuz
  • Re: macOS - Sequoia CI task is stuck on the Postgres Github CI Andres Freund
  • Re: macOS - Sequoia CI task is stuck on the Postgres Github CI Álvaro Herrera
  • Re: macOS - Sequoia CI task is stuck on the Postgres Github CI Andres Freund
• Question on PostgreSQL Table Partitioning – Performance of Queries That Do Not Use the Partition Key atma ram
  • Re: Question on PostgreSQL Table Partitioning – Performance of Queries That Do Not Use the Partition Key Aleksander Alekseev
• Second RewriteQuery complains about first RewriteQuery in edge case Bernice Southey
  • Re: Second RewriteQuery complains about first RewriteQuery in edge case Kirill Reshke
  • Re: Second RewriteQuery complains about first RewriteQuery in edge case Dean Rasheed
  • Re: Second RewriteQuery complains about first RewriteQuery in edge case Tom Lane
  • Re: Second RewriteQuery complains about first RewriteQuery in edge case Bernice Southey
  • Re: Second RewriteQuery complains about first RewriteQuery in edge case Bernice Southey
  • Re: Second RewriteQuery complains about first RewriteQuery in edge case Dean Rasheed
  • Re: Second RewriteQuery complains about first RewriteQuery in edge case Tom Lane
  • Re: Second RewriteQuery complains about first RewriteQuery in edge case Dean Rasheed
  • Re: Second RewriteQuery complains about first RewriteQuery in edge case Bernice Southey
  • Re: Second RewriteQuery complains about first RewriteQuery in edge case Dean Rasheed
  • Re: Second RewriteQuery complains about first RewriteQuery in edge case Tom Lane
  • Re: Second RewriteQuery complains about first RewriteQuery in edge case Dean Rasheed
  • Re: Second RewriteQuery complains about first RewriteQuery in edge case Dean Rasheed
  • Re: Second RewriteQuery complains about first RewriteQuery in edge case Tom Lane
  • Re: Second RewriteQuery complains about first RewriteQuery in edge case Dean Rasheed
  • Re: Second RewriteQuery complains about first RewriteQuery in edge case Bernice Southey
  • Re: Second RewriteQuery complains about first RewriteQuery in edge case Dean Rasheed
• Refactoring: Use soft error reporting for *_opt_overflow functions of date/timestamp Amul Sul
  • Re: Refactoring: Use soft error reporting for *_opt_overflow functions of date/timestamp Michael Paquier
  • Re: Refactoring: Use soft error reporting for *_opt_overflow functions of date/timestamp Amit Langote
  • Re: Refactoring: Use soft error reporting for *_opt_overflow functions of date/timestamp Amul Sul
  • Re: Refactoring: Use soft error reporting for *_opt_overflow functions of date/timestamp Michael Paquier
  • Re: Refactoring: Use soft error reporting for *_opt_overflow functions of date/timestamp Amit Langote
  • Re: Refactoring: Use soft error reporting for *_opt_overflow functions of date/timestamp Michael Paquier
  • Re: Refactoring: Use soft error reporting for *_opt_overflow functions of date/timestamp Amit Langote
  • Re: Refactoring: Use soft error reporting for *_opt_overflow functions of date/timestamp Amul Sul
  • Re: Refactoring: Use soft error reporting for *_opt_overflow functions of date/timestamp Amit Langote
  • Re: Refactoring: Use soft error reporting for *_opt_overflow functions of date/timestamp Michael Paquier
  • Re: Refactoring: Use soft error reporting for *_opt_overflow functions of date/timestamp Amul Sul
  • Re: Refactoring: Use soft error reporting for *_opt_overflow functions of date/timestamp Michael Paquier
  • Re: Refactoring: Use soft error reporting for *_opt_overflow functions of date/timestamp Amul Sul
  • Re: Refactoring: Use soft error reporting for *_opt_overflow functions of date/timestamp Michael Paquier
  • Re: Refactoring: Use soft error reporting for *_opt_overflow functions of date/timestamp Amit Langote
  • Re: Refactoring: Use soft error reporting for *_opt_overflow functions of date/timestamp Amul Sul
• Re: Support for 8-byte TOAST values (aka the TOAST infinite loop problem) Nikhil Kumar Veldanda
  • Re: Support for 8-byte TOAST values (aka the TOAST infinite loop problem) Robert Haas
• [buildfarm related] Machines gcc experimental failed test_lfind Hayato Kuroda (Fujitsu)
  • Re: [buildfarm related] Machines gcc experimental failed test_lfind John Naylor
  • Re: [buildfarm related] Machines gcc experimental failed test_lfind Tom Lane
  • Re: [buildfarm related] Machines gcc experimental failed test_lfind Nathan Bossart
  • Re: [buildfarm related] Machines gcc experimental failed test_lfind Tom Lane
  • Re: [buildfarm related] Machines gcc experimental failed test_lfind Nathan Bossart
  • RE: [buildfarm related] Machines gcc experimental failed test_lfind Hayato Kuroda (Fujitsu)
• Re: Have the planner convert COUNT(1) / COUNT(not_null_col) to COUNT(*) David Rowley
  • Re: Have the planner convert COUNT(1) / COUNT(not_null_col) to COUNT(*) David Rowley
• [PATCH] psql: add size-based sorting options (O/o) for tables and indexes M . Atıf Ceylan
  • Re: [PATCH] psql: add size-based sorting options (O/o) for tables and indexes Aleksander Alekseev
  • [PATCH] psql: add size-based sorting options (O/o) for tables and indexes M . Atıf Ceylan
  • Re: [PATCH] psql: add size-based sorting options (O/o) for tables and indexes Euler Taveira
  • Re: [PATCH] psql: add size-based sorting options (O/o) for tables and indexes Pavel Stehule
  • Re: [PATCH] psql: add size-based sorting options (O/o) for tables and indexes Pavel Stehule
  • Re: [PATCH] psql: add size-based sorting options (O/o) for tables and indexes Mahmoud Ayman
• Additional info for CREATE ROLE with REPLICATION Marcos Pegoraro
  • Re: Additional info for CREATE ROLE with REPLICATION Chao Li
  • Re: Additional info for CREATE ROLE with REPLICATION Marcos Pegoraro
  • Re: Additional info for CREATE ROLE with REPLICATION David G. Johnston
• Re: [PATCH] Add native PIVOT syntax for SQL Server/Oracle compatibility Peter Eisentraut
  • Re: [PATCH] Add native PIVOT syntax for SQL Server/Oracle compatibility Michael Paquier
  • Re: [PATCH] Add native PIVOT syntax for SQL Server/Oracle compatibility Kirill Reshke
• The pgperltidy diffs in HEAD Daniel Gustafsson
  • Re: The pgperltidy diffs in HEAD Álvaro Herrera
  • Re: The pgperltidy diffs in HEAD Tom Lane
  • Re: The pgperltidy diffs in HEAD Daniel Gustafsson
  • Re: The pgperltidy diffs in HEAD Tom Lane
  • Re: The pgperltidy diffs in HEAD Álvaro Herrera
  • Re: The pgperltidy diffs in HEAD Daniel Gustafsson
  • Re: The pgperltidy diffs in HEAD Álvaro Herrera
  • Re: The pgperltidy diffs in HEAD Daniel Gustafsson
  • Re: The pgperltidy diffs in HEAD Andrew Dunstan
  • Re: The pgperltidy diffs in HEAD Dagfinn Ilmari Mannsåker
  • Re: The pgperltidy diffs in HEAD Jacob Champion
  • Re: The pgperltidy diffs in HEAD Daniel Gustafsson
  • Re: The pgperltidy diffs in HEAD Dagfinn Ilmari Mannsåker
  • Re: The pgperltidy diffs in HEAD Daniel Gustafsson
  • Re: The pgperltidy diffs in HEAD Daniel Gustafsson
  • Re: The pgperltidy diffs in HEAD Dagfinn Ilmari Mannsåker
  • Re: The pgperltidy diffs in HEAD Tom Lane
• Re: Bypassing cursors in postgres_fdw to enable parallel plans KENAN YILMAZ
  • Re: Bypassing cursors in postgres_fdw to enable parallel plans KENAN YILMAZ
• Announcing Release 20 of the PostgreSQL Build farm Client Andrew Dunstan
• reduce size of logs stored by buildfarm Álvaro Herrera
  • Re: reduce size of logs stored by buildfarm Andres Freund
  • Re: reduce size of logs stored by buildfarm Álvaro Herrera
  • Re: reduce size of logs stored by buildfarm Tom Lane
  • Re: reduce size of logs stored by buildfarm Andrew Dunstan
  • Re: reduce size of logs stored by buildfarm Jacob Champion
  • Re: reduce size of logs stored by buildfarm Álvaro Herrera
  • Re: reduce size of logs stored by buildfarm Jacob Champion
• Some optimizations for COALESCE expressions during constant folding Richard Guo
  • Re: Some optimizations for COALESCE expressions during constant folding Tender Wang
  • Re: Some optimizations for COALESCE expressions during constant folding Richard Guo
  • Re: Some optimizations for COALESCE expressions during constant folding Dagfinn Ilmari Mannsåker
  • Re: Some optimizations for COALESCE expressions during constant folding David Rowley
  • Re: Some optimizations for COALESCE expressions during constant folding David Rowley
  • Re: Some optimizations for COALESCE expressions during constant folding Richard Guo

• Earlier messages
• Later messages