pgsql-hackers  

Messages by Thread

• • Re: allow changing autovacuum_max_workers without restarting Tom Lane
  • Re: allow changing autovacuum_max_workers without restarting Nathan Bossart
  • Re: allow changing autovacuum_max_workers without restarting Peter Eisentraut
  • Re: allow changing autovacuum_max_workers without restarting Nathan Bossart
  • Re: allow changing autovacuum_max_workers without restarting Tom Lane
  • Re: allow changing autovacuum_max_workers without restarting Nathan Bossart
  • Re: allow changing autovacuum_max_workers without restarting Tom Lane
  • Re: allow changing autovacuum_max_workers without restarting Nathan Bossart
  • Re: allow changing autovacuum_max_workers without restarting Tom Lane
  • Re: allow changing autovacuum_max_workers without restarting Nathan Bossart
• domain over virtual generated column jian he
  • Re: domain over virtual generated column jian he
• Avoid circular header file dependency Bertrand Drouvot
  • Re: Avoid circular header file dependency Tom Lane
  • Re: Avoid circular header file dependency Michael Paquier
  • Re: Avoid circular header file dependency Bertrand Drouvot
  • Re: Avoid circular header file dependency Michael Paquier
  • Re: Avoid circular header file dependency Bertrand Drouvot
  • Re: Avoid circular header file dependency Tom Lane
  • Re: Avoid circular header file dependency Bertrand Drouvot
  • Re: Avoid circular header file dependency Tom Lane
• Sanding down some edge cases for PL/pgSQL reserved words Tom Lane
  • Re: Sanding down some edge cases for PL/pgSQL reserved words Joel Jacobson
  • Re: Sanding down some edge cases for PL/pgSQL reserved words Tom Lane
  • Re: Sanding down some edge cases for PL/pgSQL reserved words Joel Jacobson
• [SP-]GiST IOS visibility bug (was: Why doens't GiST require super-exclusive lock) Matthias van de Meent
• gcc 15 "array subscript 0" warning at level -O3 Tom Lane
  • Re: gcc 15 "array subscript 0" warning at level -O3 Tom Lane
  • Re: gcc 15 "array subscript 0" warning at level -O3 Andres Freund
• Questions about logicalrep_worker_launch() Fujii Masao
  • Re: Questions about logicalrep_worker_launch() Masahiko Sawada
  • Re: Questions about logicalrep_worker_launch() Fujii Masao
  • Re: Questions about logicalrep_worker_launch() Amit Kapila
  • Re: Questions about logicalrep_worker_launch() Fujii Masao
  • Re: Questions about logicalrep_worker_launch() Amit Kapila
• gcc 15.1 warnings - jsonb_util.c Erik Rijkers
  • Re: gcc 15.1 warnings - jsonb_util.c Tom Lane
• XACT_EVENT_COMMIT placement Yurii Rashkovskii
• Re: Allow io_combine_limit up to 1MB Andres Freund
  • Re: Allow io_combine_limit up to 1MB Tom Lane
  • Re: Allow io_combine_limit up to 1MB Andres Freund
  • Re: Allow io_combine_limit up to 1MB Tom Lane
  • Re: Allow io_combine_limit up to 1MB Thomas Munro
• Introduce some randomness to autovacuum Junwang Zhao
  • Re: Introduce some randomness to autovacuum wenhui qiu
  • Re: Introduce some randomness to autovacuum Nikita Malakhov
  • Re: Introduce some randomness to autovacuum Junwang Zhao
  • Re: Introduce some randomness to autovacuum Greg Sabino Mullane
  • Re: Introduce some randomness to autovacuum Sami Imseih
  • Re: Introduce some randomness to autovacuum Robert Treat
  • Re: Introduce some randomness to autovacuum Junwang Zhao
  • Re: Introduce some randomness to autovacuum Nathan Bossart
  • Re: Introduce some randomness to autovacuum Sami Imseih
  • Re: Introduce some randomness to autovacuum David Rowley
  • Re: Introduce some randomness to autovacuum Junwang Zhao
  • Re: Introduce some randomness to autovacuum David Rowley
  • Re: Introduce some randomness to autovacuum Junwang Zhao
• Re: on_error table, saving error info to a table jian he
• Re: why in appendShellStringNoError() loop still continues even after it found CR or LF? Robert Haas
• doc: Some copy-editing around prefix operators Christoph Berg
• Re: Why doesn't GiST VACUUM require a super-exclusive lock, like nbtree VACUUM? Matthias van de Meent
• Re: Available disk space per tablespace said assemlal
• Cancel problems of query to pg_stat_statements Roman Khapov
  • Re: Cancel problems of query to pg_stat_statements Andrey Borodin
  • [PATCH v2] Re: Cancel problems of query to pg_stat_statements Roman Khapov
• Re: Improve verification of recovery_target_timeline GUC. David Steele
  • Re: Improve verification of recovery_target_timeline GUC. Michael Paquier
  • Re: Improve verification of recovery_target_timeline GUC. David Steele
• Re: Slot's restart_lsn may point to removed WAL segment after hard restart unexpectedly Vitaly Davydov
  • Re: Slot's restart_lsn may point to removed WAL segment after hard restart unexpectedly Alexander Korotkov
  • Re: Slot's restart_lsn may point to removed WAL segment after hard restart unexpectedly Masahiko Sawada
  • Re: Slot's restart_lsn may point to removed WAL segment after hard restart unexpectedly Alexander Korotkov
  • Re: Slot's restart_lsn may point to removed WAL segment after hard restart unexpectedly Masahiko Sawada
  • Re: Slot's restart_lsn may point to removed WAL segment after hard restart unexpectedly Vitaly Davydov
  • Re: Slot's restart_lsn may point to removed WAL segment after hard restart unexpectedly Alexander Korotkov
  • Re: Slot's restart_lsn may point to removed WAL segment after hard restart unexpectedly Vitaly Davydov
• Re: Showing applied extended statistics in explain Part 2 Andrei Lepikhov
• Re: MergeAppend could consider sorting cheapest child path Andrei Lepikhov
  • Re: MergeAppend could consider sorting cheapest child path Alexander Pyhalov
  • Re: MergeAppend could consider sorting cheapest child path Andrei Lepikhov
  • Re: MergeAppend could consider sorting cheapest child path Andrei Lepikhov
  • Re: MergeAppend could consider sorting cheapest child path Alexander Pyhalov
  • Re: MergeAppend could consider sorting cheapest child path Andrei Lepikhov
  • Re: MergeAppend could consider sorting cheapest child path Andrei Lepikhov
  • Re: MergeAppend could consider sorting cheapest child path Alexander Pyhalov
  • Re: MergeAppend could consider sorting cheapest child path Andrei Lepikhov
  • Re: MergeAppend could consider sorting cheapest child path Alexander Pyhalov
  • Re: MergeAppend could consider sorting cheapest child path Andrei Lepikhov
  • Re: MergeAppend could consider sorting cheapest child path Alexander Pyhalov
• pg_upgrade-breaking release Bruce Momjian
  • Re: pg_upgrade-breaking release Greg Sabino Mullane
  • Re: pg_upgrade-breaking release Bruce Momjian
  • Re: pg_upgrade-breaking release Greg Sabino Mullane
  • Re: pg_upgrade-breaking release Bruce Momjian
  • Re: pg_upgrade-breaking release Noah Misch
  • Re: pg_upgrade-breaking release Álvaro Herrera
  • Re: pg_upgrade-breaking release Bruce Momjian
• Postmaster fails to shut down right after crash restart Sergey Shinderuk
• Possible incorrect comment in ginget.c Arseniy Mukhin
• Disallow redundant indexes Japin Li
  • Re: Disallow redundant indexes David Rowley
  • Re: Disallow redundant indexes Greg Sabino Mullane
  • Re: Disallow redundant indexes Japin Li
  • Re: Disallow redundant indexes Corey Huinker
  • Re: Disallow redundant indexes Sami Imseih
  • Re: Disallow redundant indexes Nathan Bossart
  • Re: Disallow redundant indexes Euler Taveira
  • Re: Disallow redundant indexes Sami Imseih
  • Re: Disallow redundant indexes Japin Li
• Non-reproducible AIO failure Tom Lane
  • Re: Non-reproducible AIO failure Andres Freund
  • Re: Non-reproducible AIO failure Tom Lane
• Re: Making sslrootcert=system work on Windows psql George MacKerron
  • sslmode=secure by default (Re: Making sslrootcert=system work on Windows psql) Christoph Berg
  • Re: sslmode=secure by default (Re: Making sslrootcert=system work on Windows psql) George MacKerron
  • Re: sslmode=secure by default (Re: Making sslrootcert=system work on Windows psql) Christoph Berg
  • Re: sslmode=secure by default (Re: Making sslrootcert=system work on Windows psql) Peter Eisentraut
  • Re: sslmode=secure by default (Re: Making sslrootcert=system work on Windows psql) Jacob Champion
  • Re: sslmode=secure by default (Re: Making sslrootcert=system work on Windows psql) Jelte Fennema-Nio
  • Re: sslmode=secure by default (Re: Making sslrootcert=system work on Windows psql) Daniel Gustafsson
  • Re: sslmode=secure by default (Re: Making sslrootcert=system work on Windows psql) Jacob Champion
  • Re: sslmode=secure by default (Re: Making sslrootcert=system work on Windows psql) Jacob Champion
  • Re: Making sslrootcert=system work on Windows psql Jacob Champion
  • Re: Making sslrootcert=system work on Windows psql George MacKerron
  • Re: Making sslrootcert=system work on Windows psql Jelte Fennema-Nio
  • Re: Making sslrootcert=system work on Windows psql George MacKerron
  • Re: Making sslrootcert=system work on Windows psql Jelte Fennema-Nio
  • Re: Making sslrootcert=system work on Windows psql Jelte Fennema-Nio
  • Re: Making sslrootcert=system work on Windows psql George MacKerron
  • Re: Making sslrootcert=system work on Windows psql Daniel Gustafsson
  • Re: Making sslrootcert=system work on Windows psql George MacKerron
  • Re: Making sslrootcert=system work on Windows psql Daniel Gustafsson
• Re: support ALTER COLUMN SET EXPRESSION over virtual generated column with check constraint jian he
• Re: SQL:2023 JSON simplified accessor support Nikita Malakhov
• Re: Doc: fix the rewrite condition when executing ALTER TABLE ADD COLUMN Nathan Bossart
  • Re: Doc: fix the rewrite condition when executing ALTER TABLE ADD COLUMN Álvaro Herrera
  • Re: Doc: fix the rewrite condition when executing ALTER TABLE ADD COLUMN Peter Eisentraut
  • Re: Doc: fix the rewrite condition when executing ALTER TABLE ADD COLUMN Robert Treat
  • Re: Doc: fix the rewrite condition when executing ALTER TABLE ADD COLUMN Peter Eisentraut
  • Re: Doc: fix the rewrite condition when executing ALTER TABLE ADD COLUMN Robert Treat
• Startup subpaths in MergeAppend path Andrei Lepikhov
• Does RENAME TABLE rename associated identity sequence? Jason Song
  • Re: Does RENAME TABLE rename associated identity sequence? Ashutosh Bapat
  • Re: Does RENAME TABLE rename associated identity sequence? Isaac Morland
  • Re: Does RENAME TABLE rename associated identity sequence? Tom Lane
  • Re: Does RENAME TABLE rename associated identity sequence? Ashutosh Bapat
  • Re: Does RENAME TABLE rename associated identity sequence? Jason Song
• virtual generated column as partition key jian he
• extension_control_path and "directory" Christoph Berg
  • Re: extension_control_path and "directory" Matheus Alcantara
  • Re: extension_control_path and "directory" Christoph Berg
  • Re: extension_control_path and "directory" David E. Wheeler
  • Re: extension_control_path and "directory" Matheus Alcantara
  • Re: extension_control_path and "directory" Christoph Berg
  • Re: extension_control_path and "directory" Matheus Alcantara
  • Re: extension_control_path and "directory" David E. Wheeler
  • Re: extension_control_path and "directory" Matheus Alcantara
  • Re: extension_control_path and "directory" David E. Wheeler
  • Re: extension_control_path and "directory" Matheus Alcantara
  • Re: extension_control_path and "directory" David E. Wheeler
  • Re: extension_control_path and "directory" Matheus Alcantara
  • Re: extension_control_path and "directory" David E. Wheeler
  • Re: extension_control_path and "directory" Matheus Alcantara
  • Re: extension_control_path and "directory" David E. Wheeler
  • Re: extension_control_path and "directory" Peter Eisentraut
  • Re: extension_control_path and "directory" Matheus Alcantara
  • Re: extension_control_path and "directory" Christoph Berg
• [PATCH] dynahash: add memory allocation failure check m . korotkov
  • Re: [PATCH] dynahash: add memory allocation failure check Andrey Borodin
  • Re: [PATCH] dynahash: add memory allocation failure check m . korotkov
  • Re: [PATCH] dynahash: add memory allocation failure check Aleksander Alekseev
  • Re: [PATCH] dynahash: add memory allocation failure check Tom Lane
  • Re: [PATCH] dynahash: add memory allocation failure check Andrey Borodin
  • Re: [PATCH] dynahash: add memory allocation failure check Tom Lane
  • Re: [PATCH] dynahash: add memory allocation failure check Andrey Borodin
• Avoid core dump in pgstat_read_statsfile() Bertrand Drouvot
  • Re: Avoid core dump in pgstat_read_statsfile() Michael Paquier
• Re: Row pattern recognition Tatsuo Ishii
  • Re: Row pattern recognition Tatsuo Ishii
• DOCS - create publication (tweak for generated columns) Peter Smith
  • Re: DOCS - create publication (tweak for generated columns) David G. Johnston
  • Re: DOCS - create publication (tweak for generated columns) Peter Smith
  • Re: DOCS - create publication (tweak for generated columns) Amit Kapila
  • Re: DOCS - create publication (tweak for generated columns) Peter Smith
  • Re: DOCS - create publication (tweak for generated columns) Amit Kapila
• Re: Enable data checksums by default Tomas Vondra
  • Re: Enable data checksums by default Christoph Berg
  • Re: Enable data checksums by default Peter Eisentraut
• Re: pgsql: Update guidance for running vacuumdb after pg_upgrade. Christoph Berg
  • Re: pgsql: Update guidance for running vacuumdb after pg_upgrade. Nathan Bossart
  • Re: pgsql: Update guidance for running vacuumdb after pg_upgrade. Christoph Berg
  • Re: pgsql: Update guidance for running vacuumdb after pg_upgrade. Nathan Bossart
  • Re: pgsql: Update guidance for running vacuumdb after pg_upgrade. Christoph Berg
  • vacuumdb --missing-stats-only and pg_upgrade from PG13 Christoph Berg
  • Re: vacuumdb --missing-stats-only and pg_upgrade from PG13 Nathan Bossart
  • Re: vacuumdb --missing-stats-only and pg_upgrade from PG13 Christoph Berg
  • Re: vacuumdb --missing-stats-only and pg_upgrade from PG13 Nathan Bossart
  • Re: vacuumdb --missing-stats-only and pg_upgrade from PG13 Christoph Berg
  • Re: vacuumdb --missing-stats-only and pg_upgrade from PG13 Nathan Bossart
• Re: index prefetching Peter Geoghegan

• Earlier messages
• Later messages