pgsql-hackers  

Messages by Thread

• • Re: [PATCH v1] Fix races in Windows pthread emulation Alexander Lakhin
  • Re: [PATCH v1] Fix races in Windows pthread emulation Harrison Booth
  • Re: [PATCH v2] Fix races in Windows pthread emulation harrisontbooth
  • Re: [PATCH v2] Fix races in Windows pthread emulation Heikki Linnakangas
  • Re: [PATCH v2] Fix races in Windows pthread emulation Harrison Booth
  • Re: [PATCH v2] Fix races in Windows pthread emulation Alexander Lakhin
• Re: Parallel Apply vignesh C
  • Re: Parallel Apply vignesh C
  • Re: Parallel Apply Zhijie Hou
  • Re: Parallel Apply vignesh C
  • Re: Parallel Apply vignesh C
  • Re: Parallel Apply vignesh C
  • Re: Parallel Apply Zhijie Hou
  • Re: Parallel Apply Shlok Kyal
  • Re: Parallel Apply Zhijie Hou
  • Re: Parallel Apply Shlok Kyal
  • Re: Parallel Apply vignesh C
  • Re: Parallel Apply Manu
• Re: [PATCH] pg_upgrade: add --initdb option to create the new cluster automatically Heikki Linnakangas
  • Re: [PATCH] pg_upgrade: add --initdb option to create the new cluster automatically Heikki Linnakangas
  • Re: [PATCH] pg_upgrade: add --initdb option to create the new cluster automatically Bohyun Lee
  • Re: [PATCH] pg_upgrade: add --initdb option to create the new cluster automatically Heikki Linnakangas
  • Re: [PATCH] pg_upgrade: add --initdb option to create the new cluster automatically Bohyun Lee
  • Re: [PATCH] pg_upgrade: add --initdb option to create the new cluster automatically Heikki Linnakangas
• Re: pg_dump/restore failure (dependency?) on BF serinus Kirill Reshke
  • Re: pg_dump/restore failure (dependency?) on BF serinus Kirill Reshke
  • Re: pg_dump/restore failure (dependency?) on BF serinus Álvaro Herrera
  • Re: pg_dump/restore failure (dependency?) on BF serinus Kirill Reshke
• Re: [PATCH v1] amcheck: Allow interrupting the child-level rightlink walk Heikki Linnakangas
• Re: amcheck: add index-all-keys-match verification for B-Tree Jakub Wartak
• Re: Improving scalability of Parallel Bitmap Heap/Index Scan David Geier
  • Re: Improving scalability of Parallel Bitmap Heap/Index Scan John Naylor
  • Re: Improving scalability of Parallel Bitmap Heap/Index Scan David Geier
  • Re: Improving scalability of Parallel Bitmap Heap/Index Scan David Geier
  • Re: Improving scalability of Parallel Bitmap Heap/Index Scan John Naylor
  • Re: Improving scalability of Parallel Bitmap Heap/Index Scan David Geier
  • Re: Improving scalability of Parallel Bitmap Heap/Index Scan David Geier
  • Re: Improving scalability of Parallel Bitmap Heap/Index Scan John Naylor
  • Re: Improving scalability of Parallel Bitmap Heap/Index Scan John Naylor
  • Re: Improving scalability of Parallel Bitmap Heap/Index Scan David Geier
  • Re: Improving scalability of Parallel Bitmap Heap/Index Scan shihao zhong
  • Re: Improving scalability of Parallel Bitmap Heap/Index Scan David Geier
  • Re: Improving scalability of Parallel Bitmap Heap/Index Scan shihao zhong
  • Re: Improving scalability of Parallel Bitmap Heap/Index Scan David Geier
  • Re: Improving scalability of Parallel Bitmap Heap/Index Scan David Geier
  • Re: Improving scalability of Parallel Bitmap Heap/Index Scan Osama Abdul Qader
  • Re: Improving scalability of Parallel Bitmap Heap/Index Scan John Naylor
  • Re: Improving scalability of Parallel Bitmap Heap/Index Scan David Geier
  • Re: Improving scalability of Parallel Bitmap Heap/Index Scan John Naylor
  • Re: Improving scalability of Parallel Bitmap Heap/Index Scan David Geier
• pg_plan_advice fails on a CustomScan that replaces a join Dongpo Liu
• Re: pgstat: allow a stats kind to use its own dedicated dsa/dshash Michael Paquier
  • Re: 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 Sami Imseih
  • Re: pgstat: allow a stats kind to use its own dedicated dsa/dshash Michael Paquier
  • Re: 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 Michael Paquier
  • Re: 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 Michael Paquier
  • Re: 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 Michael Paquier
  • Re: 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 Zsolt Parragi
  • Re: 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 Michael Paquier
  • Re: pgstat: allow a stats kind to use its own dedicated dsa/dshash Zsolt Parragi
  • Re: 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 Tom Lane
  • Re: 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 Michael Paquier
  • Re: pgstat: allow a stats kind to use its own dedicated dsa/dshash Alexander Lakhin
  • Re: pgstat: allow a stats kind to use its own dedicated dsa/dshash Michael Paquier
  • Re: pgstat: allow a stats kind to use its own dedicated dsa/dshash Alexander Lakhin
• pg_resetwal: add --cluster-state option shihao zhong
  • Re: pg_resetwal: add --cluster-state option Sho Ito
  • Re: pg_resetwal: add --cluster-state option Chao Li
  • Re: pg_resetwal: add --cluster-state option shihao zhong
  • Re: pg_resetwal: add --cluster-state option Sho Ito
• Re: examine_variable ignored CollateExpr shihao zhong
  • Re: examine_variable ignored CollateExpr ZizhuanLiu X-MAN
  • Re: examine_variable ignored CollateExpr shihao zhong
  • Re: examine_variable ignored CollateExpr ZizhuanLiu X-MAN
  • Re: examine_variable ignored CollateExpr ZizhuanLiu X-MAN
• [PATCH] pg_walsummary: suppress limit output with --quiet Koshi Shibagaki (Fujitsu)
  • RE: [PATCH] pg_walsummary: suppress limit output with --quiet Hayato Kuroda (Fujitsu)
  • Re: [PATCH] pg_walsummary: suppress limit output with --quiet Koshi Shibagaki (Fujitsu)
  • Re: [PATCH] pg_walsummary: suppress limit output with --quiet Fujii Masao
  • Re: [PATCH] pg_walsummary: suppress limit output with --quiet Koshi Shibagaki (Fujitsu)
  • RE: [PATCH] pg_walsummary: suppress limit output with --quiet Hayato Kuroda (Fujitsu)
  • Re: [PATCH] pg_walsummary: suppress limit output with --quiet Fujii Masao
  • RE: [PATCH] pg_walsummary: suppress limit output with --quiet Hayato Kuroda (Fujitsu)
  • Re: [PATCH] pg_walsummary: suppress limit output with --quiet Fujii Masao
  • Re: [PATCH] pg_walsummary: suppress limit output with --quiet Fujii Masao
• Re: Support specialized B-tree page searches Yao Feng
• Re: issues with eager aggregation Richard Guo
  • Re: issues with eager aggregation Richard Guo
• Show effective xmin in pg_replication_slots when xmin is not set Bharath Rupireddy
  • Re: Show effective xmin in pg_replication_slots when xmin is not set Nisha Moond
  • Re: Show effective xmin in pg_replication_slots when xmin is not set Sami Imseih
  • Re: Show effective xmin in pg_replication_slots when xmin is not set Andres Freund
• Limiting WAL retained for archiving, like max_slot_wal_keep_size Joao Detomini
  • Re: Limiting WAL retained for archiving, like max_slot_wal_keep_size surya poondla
  • Limiting WAL retained for archiving, like max_slot_wal_keep_size Joao Detomini
  • Re: Limiting WAL retained for archiving, like max_slot_wal_keep_size Matthias van de Meent
  • Re: Limiting WAL retained for archiving, like max_slot_wal_keep_size Joao Detomini
• Re: Asynchronous MergeAppend Alexander Korotkov
  • Re: Asynchronous MergeAppend Etsuro Fujita
  • Re: Asynchronous MergeAppend Etsuro Fujita
  • Re: Asynchronous MergeAppend solai v
• Planning time quadratic in the IN-list length for "c = X AND (a, b) IN (...)" with BitmapOr Stefan Guha
  • Re: Planning time quadratic in the IN-list length for "c = X AND (a, b) IN (...)" with BitmapOr Manu
  • Re: Planning time quadratic in the IN-list length for "c = X AND (a, b) IN (...)" with BitmapOr Stefan Guha
  • Re: Planning time quadratic in the IN-list length for "c = X AND (a, b) IN (...)" with BitmapOr Manu
  • Re: Planning time quadratic in the IN-list length for "c = X AND (a, b) IN (...)" with BitmapOr Stefan Guha
  • Re: Planning time quadratic in the IN-list length for "c = X AND (a, b) IN (...)" with BitmapOr Manu
• Table Function Scan can report incorrect "Maximum Storage" in EXPLAIN Tatsuya Kawata
  • Re: Table Function Scan can report incorrect "Maximum Storage" in EXPLAIN David Rowley
  • Re: Table Function Scan can report incorrect "Maximum Storage" in EXPLAIN Tatsuya Kawata
• amcheck: detect corruption from the recent snapshot-export bug Andrey Borodin
  • Re: amcheck: detect corruption from the recent snapshot-export bug Mark Dilger
  • Re: amcheck: detect corruption from the recent snapshot-export bug Andrey Borodin
• [PATCH] Fix default partition validation for reordered child columns CharSyam
• [PROPOSAL] Isolated copy-on-write cluster forks Lucas Jeffrey
• Re: [PATCH] Add planner support function to two-argument regexp_like() jian he
  • Re: [PATCH] Add planner support function to two-argument regexp_like() shihao zhong
  • Re: [PATCH] Add planner support function to two-argument regexp_like() shihao zhong
• Re: pg_dump: fix NOT NULL constraint name comparison using makeObjectName JoongHyuk Shin
• Re: ERROR: no relation entry for relid 3 Richard Guo
• Re: Checkpointer write combining shihao zhong
• Re: UNDO with constant time recovery (CTR) shihao zhong
  • Re: UNDO with constant time recovery (CTR) Greg Burd
  • Re: UNDO with constant time recovery (CTR) Matthias van de Meent
  • Re: UNDO with constant time recovery (CTR) Manu
  • Re: UNDO with constant time recovery (CTR) Greg Burd
  • Re: UNDO with constant time recovery (CTR) Greg Burd
  • Re: UNDO with constant time recovery (CTR) Matthias van de Meent
  • Re: UNDO with constant time recovery (CTR) Greg Burd
  • Re: UNDO with constant time recovery (CTR) Matthias van de Meent
• Re: Copy from JSON FORMAT. Junwang Zhao
• Re: Unprocessed SubLink from whole-row join alias expansion Richard Guo
• Re: Proposal: "query_work_mem" GUC, to distribute working memory to the query's individual operators Manu
  • Re: Proposal: "query_work_mem" GUC, to distribute working memory to the query's individual operators Jeff Davis
  • Re: Proposal: "query_work_mem" GUC, to distribute working memory to the query's individual operators Manu
• Re: [PATCH] Refactor pgbench to make future improvements easier Zsolt Parragi
  • Re: [PATCH] Refactor pgbench to make future improvements easier Hannu Krosing
  • Re: [PATCH] Refactor pgbench to make future improvements easier Hannu Krosing
• Re: Proposal: SELECT * EXCLUDE (...) command Kacper Kuras
  • Re: Proposal: SELECT * EXCLUDE (...) command Hunaid Sohail
  • Re: Proposal: SELECT * EXCLUDE (...) command Robert Treat
  • Re: Proposal: SELECT * EXCLUDE (...) command Hunaid Sohail
  • Re: Proposal: SELECT * EXCLUDE (...) command Marcos Pegoraro
  • Re: Proposal: SELECT * EXCLUDE (...) command Hunaid Sohail
  • Re: Proposal: SELECT * EXCLUDE (...) command Kacper Kuras
  • Re: Proposal: SELECT * EXCLUDE (...) command Hunaid Sohail
  • Re: Proposal: SELECT * EXCLUDE (...) command Kacper Kuras
• Check for non-deterministic FK collations before upgrade Kirill Reshke
  • Re: Check for non-deterministic FK collations before upgrade Andrey Borodin
• Re: Coverage with make coverage-html is broken on latest Debian using lcov v2 Tom Lane
  • Re: Coverage with make coverage-html is broken on latest Debian using lcov v2 Tom Lane
  • Re: Coverage with make coverage-html is broken on latest Debian using lcov v2 Álvaro Herrera
  • Re: Coverage with make coverage-html is broken on latest Debian using lcov v2 Tom Lane
  • Re: Coverage with make coverage-html is broken on latest Debian using lcov v2 Andres Freund
  • Re: Coverage with make coverage-html is broken on latest Debian using lcov v2 Álvaro Herrera
  • Re: Coverage with make coverage-html is broken on latest Debian using lcov v2 Andres Freund
  • Re: Coverage with make coverage-html is broken on latest Debian using lcov v2 Andres Freund
• How to run test coverage on Debian 13 ? Pierre Forstmann
  • Re: How to run test coverage on Debian 13 ? Tom Lane
  • Re: How to run test coverage on Debian 13 ? Álvaro Herrera
  • Re: How to run test coverage on Debian 13 ? Pierre Forstmann
• Re: Add ASCII fast path to Unicode normalization functions Andrew Dunstan
  • Re: Add ASCII fast path to Unicode normalization functions Ayush Tiwari
  • Re: Add ASCII fast path to Unicode normalization functions Andrew Dunstan
  • Re: Add ASCII fast path to Unicode normalization functions Rui Zhao
  • Re: Add ASCII fast path to Unicode normalization functions Andrew Dunstan
  • Re: Add ASCII fast path to Unicode normalization functions Tristan Partin
  • Re: Add ASCII fast path to Unicode normalization functions Andrew Dunstan
• Re: gist_trgm_ops '=' operator: planner picks it over btree, ~300x slower Andrew Dunstan
  • Re: gist_trgm_ops '=' operator: planner picks it over btree, ~300x slower Vaibhav Dalvi
  • Re: gist_trgm_ops '=' operator: planner picks it over btree, ~300x slower Vaibhav Dalvi
  • Re: gist_trgm_ops '=' operator: planner picks it over btree, ~300x slower Vaibhav Dalvi
• Re: [Patch]The Case For WAL-Logging pg_upgrade John Naylor
• Re: [PATCH] Fix pg_dump emitting OVERRIDING SYSTEM VALUE for tables with dropped identity columns shihao zhong
  • Re: [PATCH] Fix pg_dump emitting OVERRIDING SYSTEM VALUE for tables with dropped identity columns Fujii Masao
• Re: support parameterized (LATERAL) foreign joins Nurlan Tulemisov
  • Re: support parameterized (LATERAL) foreign joins vaibhave postgres
• Fix reindexdb with parallel index-level conrurrent run Kirill Reshke
  • Re: Fix reindexdb with parallel index-level conrurrent run Manu
  • Re: Fix reindexdb with parallel index-level conrurrent run Michael Paquier
  • Re: Fix reindexdb with parallel index-level conrurrent run Manu
  • Re: Fix reindexdb with parallel index-level conrurrent run Michael Paquier
  • Re: Fix reindexdb with parallel index-level conrurrent run Kirill Reshke
  • Re: Fix reindexdb with parallel index-level conrurrent run Michael Paquier
  • Re: Fix reindexdb with parallel index-level conrurrent run Michael Paquier
  • Re: Fix reindexdb with parallel index-level conrurrent run Manu
• regress: query discrepancy between explain vs execution Matthias van de Meent
  • Re: regress: query discrepancy between explain vs execution Pierre Forstmann
  • Re: regress: query discrepancy between explain vs execution David Rowley
  • Re: regress: query discrepancy between explain vs execution Matthias van de Meent
  • Re: regress: query discrepancy between explain vs execution David Rowley
• Re: Fix GROUP BY ALL handling of ORDER BY operator semantics David Christensen

• Earlier messages
• Later messages