pgsql-hackers  

Messages by Thread

• • Re: Avoid repeated scans of the output buffer in oidvectortypes() David Rowley
  • Re: Avoid repeated scans of the output buffer in oidvectortypes() Tom Lane
  • Re: Avoid repeated scans of the output buffer in oidvectortypes() Heikki Linnakangas
  • Re: Avoid repeated scans of the output buffer in oidvectortypes() Chao Li
  • Re: Avoid repeated scans of the output buffer in oidvectortypes() Chao Li
• Re: Randomize B-Tree page split location to avoid oscillating patterns Dmitry Dolgov
• Re: Fix doc: explanation of how postgres works when OOM killer is invoked Takeshi Ideriha
  • Re: Fix doc: explanation of how postgres works when OOM killer is invoked Fujii Masao
  • Re: Fix doc: explanation of how postgres works when OOM killer is invoked Takeshi Ideriha
  • Re: Fix doc: explanation of how postgres works when OOM killer is invoked Fujii Masao
  • Re: Fix doc: explanation of how postgres works when OOM killer is invoked Takeshi Ideriha
  • Re: Fix doc: explanation of how postgres works when OOM killer is invoked C W
• Re: Publication of same parent table with ONLY-ness mismatch should error Takeshi Ideriha
  • Re: Publication of same parent table with ONLY-ness mismatch should error Peter Smith
  • Re: Publication of same parent table with ONLY-ness mismatch should error shveta malik
  • Re: Publication of same parent table with ONLY-ness mismatch should error Peter Smith
  • Re: Publication of same parent table with ONLY-ness mismatch should error shveta malik
  • Re: Publication of same parent table with ONLY-ness mismatch should error Peter Smith
  • Re: Publication of same parent table with ONLY-ness mismatch should error kedar anavardekar
  • Re: Publication of same parent table with ONLY-ness mismatch should error Peter Smith
  • Re: Publication of same parent table with ONLY-ness mismatch should error Peter Smith
  • Re: Publication of same parent table with ONLY-ness mismatch should error shveta malik
  • Re: Publication of same parent table with ONLY-ness mismatch should error Chao Li
  • Re: Publication of same parent table with ONLY-ness mismatch should error Peter Smith
  • Re: Publication of same parent table with ONLY-ness mismatch should error Peter Smith
• [PATCH] plpgsql: detoast a returned record before keeping it in a non-atomic context Muzzammil Sarwar
• RE: [PATCH] Preserve replication origin OIDs in pg_upgrade Hayato Kuroda (Fujitsu)
  • Re: [PATCH] Preserve replication origin OIDs in pg_upgrade Ajin Cherian
  • Re: [PATCH] Preserve replication origin OIDs in pg_upgrade Ajin Cherian
  • 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 Ajin Cherian
• RE: Patch for migration of the pg_commit_ts directory Hayato Kuroda (Fujitsu)
  • Re: Patch for migration of the pg_commit_ts directory Maxim Orlov
  • Re: Patch for migration of the pg_commit_ts directory Ajin Cherian
• Re: DDL deparse Nikhil Sontakke
  • Re: DDL deparse Masahiko Sawada
• [PG19] Indexes from 18 miss rows after pg_upgrade shihao zhong
  • Re: [PG19] Indexes from 18 miss rows after pg_upgrade Jeff Davis
  • Re: [PG19] Indexes from 18 miss rows after pg_upgrade shihao zhong
  • Re: [PG19] Indexes from 18 miss rows after pg_upgrade Andreas Karlsson
  • Re: [PG19] Indexes from 18 miss rows after pg_upgrade shihao zhong
  • Re: [PG19] Indexes from 18 miss rows after pg_upgrade Jeff Davis
  • Re: [PG19] Indexes from 18 miss rows after pg_upgrade shihao zhong
  • Re: [PG19] Indexes from 18 miss rows after pg_upgrade Jeff Davis
• [PG19] Promotion hangs behind a backend blocked on a stuck client shihao zhong
  • Re: [PG19] Promotion hangs behind a backend blocked on a stuck client Fujii Masao
  • Re: [PG19] Promotion hangs behind a backend blocked on a stuck client Manu
  • Re: [PG19] Promotion hangs behind a backend blocked on a stuck client Fujii Masao
  • Re: [PG19] Promotion hangs behind a backend blocked on a stuck client Masahiko Sawada
  • Re: [PG19] Promotion hangs behind a backend blocked on a stuck client Fujii Masao
  • Re: [PG19] Promotion hangs behind a backend blocked on a stuck client Manu
  • Re: [PG19] Promotion hangs behind a backend blocked on a stuck client Manu
  • Re: [PG19] Promotion hangs behind a backend blocked on a stuck client shihao zhong
  • Re: [PG19] Promotion hangs behind a backend blocked on a stuck client Manu
  • Re: [PG19] Promotion hangs behind a backend blocked on a stuck client Masahiko Sawada
  • Re: [PG19] Promotion hangs behind a backend blocked on a stuck client Manu
  • Re: [PG19] Promotion hangs behind a backend blocked on a stuck client shihao zhong
  • Re: [PG19] Promotion hangs behind a backend blocked on a stuck client Masahiko Sawada
  • Re: [PG19] Promotion hangs behind a backend blocked on a stuck client shihao zhong
  • Re: [PG19] Promotion hangs behind a backend blocked on a stuck client Manu
  • Re: [PG19] Promotion hangs behind a backend blocked on a stuck client Amit Kapila
  • Re: [PG19] Promotion hangs behind a backend blocked on a stuck client Masahiko Sawada
  • Re: [PG19] Promotion hangs behind a backend blocked on a stuck client shihao zhong
  • Re: [PG19] Promotion hangs behind a backend blocked on a stuck client Amit Kapila
  • RE: [PG19] Promotion hangs behind a backend blocked on a stuck client Hayato Kuroda (Fujitsu)
  • Re: [PG19] Promotion hangs behind a backend blocked on a stuck client shihao zhong
  • Re: [PG19] Promotion hangs behind a backend blocked on a stuck client Amit Kapila
  • Re: [PG19] Promotion hangs behind a backend blocked on a stuck client Manu
  • Re: [PG19] Promotion hangs behind a backend blocked on a stuck client shihao zhong
  • Re: [PG19] Promotion hangs behind a backend blocked on a stuck client Manu
  • Re: [PG19] Promotion hangs behind a backend blocked on a stuck client shveta malik
  • RE: [PG19] Promotion hangs behind a backend blocked on a stuck client Hayato Kuroda (Fujitsu)
  • Re: [PG19] Promotion hangs behind a backend blocked on a stuck client Amit Kapila
  • Re: [PG19] Promotion hangs behind a backend blocked on a stuck client shveta malik
  • RE: [PG19] Promotion hangs behind a backend blocked on a stuck client Hayato Kuroda (Fujitsu)
  • Re: [PG19] Promotion hangs behind a backend blocked on a stuck client Zhijie Hou
  • Re: [PG19] Promotion hangs behind a backend blocked on a stuck client Amit Kapila
  • Re: [PG19] Promotion hangs behind a backend blocked on a stuck client Masahiko Sawada
  • Re: [PG19] Promotion hangs behind a backend blocked on a stuck client Masahiko Sawada
  • Re: [PG19] Promotion hangs behind a backend blocked on a stuck client Zhijie Hou
  • Re: [PG19] Promotion hangs behind a backend blocked on a stuck client Manu
  • Re: [PG19] Promotion hangs behind a backend blocked on a stuck client shihao zhong
  • Re: [PG19] Promotion hangs behind a backend blocked on a stuck client Manu
  • Re: [PG19] Promotion hangs behind a backend blocked on a stuck client Alexander Lakhin
  • Re: [PG19] Promotion hangs behind a backend blocked on a stuck client Manu
  • RE: [PG19] Promotion hangs behind a backend blocked on a stuck client Hayato Kuroda (Fujitsu)
• Weird usages of sentinel_ok() David Rowley
  • Re: Weird usages of sentinel_ok() shihao zhong
  • Re: Weird usages of sentinel_ok() David Rowley
  • Re: Weird usages of sentinel_ok() David Rowley
• Re: [PATCH] vacuumdb: Add --exclude-database option Ben Mejia
• Re: Optimize MCV stats for sortable types and utilize sorted-order properties ZizhuanLiu X-MAN
  • Re: Optimize MCV stats for sortable types and utilize sorted-order properties ZizhuanLiu X-MAN
  • Re: Optimize MCV stats for sortable types and utilize sorted-order properties ZizhuanLiu X-MAN
  • Re: Optimize MCV stats for sortable types and utilize sorted-order properties ZizhuanLiu X-MAN
• Re: [PATCH] Report no unpinned buffers as insufficient resources Fujii Masao
  • Re: [PATCH] Report no unpinned buffers as insufficient resources Ma Xueting
  • Re: [PATCH] Report no unpinned buffers as insufficient resources Fujii Masao
  • Re: [PATCH] Report no unpinned buffers as insufficient resources Fujii Masao
  • Re: [PATCH] Report no unpinned buffers as insufficient resources solai v
• Re: parallel data loading for pgbench -i Mircea Cadariu
  • Re: parallel data loading for pgbench -i Koshi Shibagaki (Fujitsu)
• Re: updates for handling optional argument in system functions Mark Wong
• Re: Incorrect CONTEXT reported for errors from parallel apply worker in logical replication Takeshi Ideriha
  • RE: Incorrect CONTEXT reported for errors from parallel apply worker in logical replication Hayato Kuroda (Fujitsu)
  • Re: Incorrect CONTEXT reported for errors from parallel apply worker in logical replication Takeshi Ideriha
  • RE: Incorrect CONTEXT reported for errors from parallel apply worker in logical replication Hayato Kuroda (Fujitsu)
  • Re: Incorrect CONTEXT reported for errors from parallel apply worker in logical replication Ajin Cherian
  • RE: Incorrect CONTEXT reported for errors from parallel apply worker in logical replication Hayato Kuroda (Fujitsu)
  • Re: Incorrect CONTEXT reported for errors from parallel apply worker in logical replication vignesh C
  • RE: Incorrect CONTEXT reported for errors from parallel apply worker in logical replication Hayato Kuroda (Fujitsu)
  • Re: Incorrect CONTEXT reported for errors from parallel apply worker in logical replication vignesh C
  • Re: Incorrect CONTEXT reported for errors from parallel apply worker in logical replication Amit Kapila
  • RE: Incorrect CONTEXT reported for errors from parallel apply worker in logical replication Hayato Kuroda (Fujitsu)
  • Re: Incorrect CONTEXT reported for errors from parallel apply worker in logical replication vignesh C
  • Re: Incorrect CONTEXT reported for errors from parallel apply worker in logical replication Dilip Kumar
  • Re: Incorrect CONTEXT reported for errors from parallel apply worker in logical replication Amit Kapila
  • Re: Incorrect CONTEXT reported for errors from parallel apply worker in logical replication Dilip Kumar
  • Re: Incorrect CONTEXT reported for errors from parallel apply worker in logical replication vignesh C
  • Re: Incorrect CONTEXT reported for errors from parallel apply worker in logical replication Zhijie Hou
  • Re: Incorrect CONTEXT reported for errors from parallel apply worker in logical replication Amit Kapila
• Re: PG19: two RI fast-path issues found while testing the batching revert Melanie Plageman
  • Re: PG19: two RI fast-path issues found while testing the batching revert Amit Langote
  • Re: PG19: two RI fast-path issues found while testing the batching revert Amit Langote
  • Re: PG19: two RI fast-path issues found while testing the batching revert Fujii Masao
  • Re: PG19: two RI fast-path issues found while testing the batching revert Amit Langote
  • Re: PG19: two RI fast-path issues found while testing the batching revert Amit Langote
  • Re: PG19: two RI fast-path issues found while testing the batching revert Amit Langote
  • Re: PG19: two RI fast-path issues found while testing the batching revert Amit Langote
  • Re: PG19: two RI fast-path issues found while testing the batching revert Amit Langote
• Re: meson: pass OpenSSL/ICU include dirs to extensions Aidar Imamov
  • Re: meson: pass OpenSSL/ICU include dirs to extensions Aidar Imamov
  • Re: meson: pass OpenSSL/ICU include dirs to extensions Harrison Booth
  • Re: meson: pass OpenSSL/ICU include dirs to extensions Aidar Imamov
  • Re: meson: pass OpenSSL/ICU include dirs to extensions Aidar Imamov
  • Re: meson: pass OpenSSL/ICU include dirs to extensions Grigorev Jurij
• Re: SQL-level pg_datum_image_equal Matthias van de Meent
  • Re: SQL-level pg_datum_image_equal Greg Burd
• Re: log XLogPrefetch stats at end of recovery Jakub Wartak
  • Re: log XLogPrefetch stats at end of recovery Ashutosh Sharma
  • Re: log XLogPrefetch stats at end of recovery Bharath Rupireddy
  • Re: log XLogPrefetch stats at end of recovery Ashutosh Sharma
  • Re: log XLogPrefetch stats at end of recovery Bharath Rupireddy
• Re: [PATCH v1] Batch B-tree TIDs when building a bitmap David Geier
  • Re: [PATCH v1] Batch B-tree TIDs when building a bitmap Haibo Yan
  • Re: [PATCH v1] Batch B-tree TIDs when building a bitmap David Geier
  • Re: [PATCH v1] Batch B-tree TIDs when building a bitmap Peter Geoghegan
  • Re: [PATCH v1] Batch B-tree TIDs when building a bitmap John Naylor
• Re: Continuous re-validation of session credentials Jakub Wartak
  • Re: Continuous re-validation of session credentials Daniel Gustafsson
• Re: Skip prefetch for block references that follow a FPW or WILL_INIT of the same block Ashutosh Sharma
  • Re: Skip prefetch for block references that follow a FPW or WILL_INIT of the same block CyberNative AI
  • Re: Skip prefetch for block references that follow a FPW or WILL_INIT of the same block Valeriy Degtyarev
  • Re: Skip prefetch for block references that follow a FPW or WILL_INIT of the same block Bharath Rupireddy
  • Re: Skip prefetch for block references that follow a FPW or WILL_INIT of the same block shihao zhong
  • Re: Skip prefetch for block references that follow a FPW or WILL_INIT of the same block Jeremy Schneider
  • Re: Skip prefetch for block references that follow a FPW or WILL_INIT of the same block Jeremy Schneider
  • Re: Skip prefetch for block references that follow a FPW or WILL_INIT of the same block shihao zhong
  • Re: Skip prefetch for block references that follow a FPW or WILL_INIT of the same block Jeremy Schneider
  • Re: Skip prefetch for block references that follow a FPW or WILL_INIT of the same block Jeremy Schneider
  • Re: Skip prefetch for block references that follow a FPW or WILL_INIT of the same block shihao zhong
  • Re: Skip prefetch for block references that follow a FPW or WILL_INIT of the same block Tomas Vondra
  • Re: Skip prefetch for block references that follow a FPW or WILL_INIT of the same block shihao zhong
  • Re: Skip prefetch for block references that follow a FPW or WILL_INIT of the same block Thomas Munro
• Fix numeric log() with an infinite value and 0<base<=1 Chao Li
  • Re: Fix numeric log() with an infinite value and 0<base<=1 Matthias van de Meent
  • Re: Fix numeric log() with an infinite value and 0<base<=1 Tom Lane
  • Re: Fix numeric log() with an infinite value and 0<base<=1 Chao Li
  • Re: Fix numeric log() with an infinite value and 0<base<=1 Matthias van de Meent
  • Re: Fix numeric log() with an infinite value and 0<base<=1 Tom Lane
  • Re: Fix numeric log() with an infinite value and 0<base<=1 Chao Li
• Perf: Specialize ExecIndexOnlyScan() like ExecSeqScan() Matthias Dötsch
  • Re: Perf: Specialize ExecIndexOnlyScan() like ExecSeqScan() Haibo Yan
  • Re: Perf: Specialize ExecIndexOnlyScan() like ExecSeqScan() Andres Freund
  • Re: Perf: Specialize ExecIndexOnlyScan() like ExecSeqScan() Haibo Yan
  • Re: Perf: Specialize ExecIndexOnlyScan() like ExecSeqScan() Matthias Dötsch
  • Re: Perf: Specialize ExecIndexOnlyScan() like ExecSeqScan() Haibo Yan
  • Re: Perf: Specialize ExecIndexOnlyScan() like ExecSeqScan() David Geier
• Re: SSI: A patch for a Serializability violation Vaijayanti Bharadwaj
• Fix pg_restore gzip stream validation (bug #19754) Chao Li
  • Re: Fix pg_restore gzip stream validation (bug #19754) Chao Li
  • Re: Fix pg_restore gzip stream validation (bug #19754) stefangrassl
  • Re: Fix pg_restore gzip stream validation (bug #19754) Chao Li
  • Re: Fix pg_restore gzip stream validation (bug #19754) Daniel Gustafsson
• Incorrect argument passed to buffer_readv_encode_error() Antonin Houska
  • Re: Incorrect argument passed to buffer_readv_encode_error() Steven Niu
  • Re: Incorrect argument passed to buffer_readv_encode_error() Michael Paquier
• Re: "failed to build any N-way joins" from a five-relation query Richard Guo
• Re: CAST(... ON DEFAULT) - WIP build on top of Error-Safe User Functions Corey Huinker
  • Re: CAST(... ON DEFAULT) - WIP build on top of Error-Safe User Functions Corey Huinker
• Re: generic plans and "initial" pruning Manu
• Parallel vacuum: workers together with leader could overrun cost budget Bharath Rupireddy
  • Re: Parallel vacuum: workers together with leader could overrun cost budget Masahiko Sawada
  • Re: Parallel vacuum: workers together with leader could overrun cost budget Bharath Rupireddy
  • Re: Parallel vacuum: workers together with leader could overrun cost budget Masahiko Sawada
  • Re: Parallel vacuum: workers together with leader could overrun cost budget Bharath Rupireddy
  • Re: Parallel vacuum: workers together with leader could overrun cost budget Chao Li
  • Re: Parallel vacuum: workers together with leader could overrun cost budget Bharath Rupireddy
  • Re: Parallel vacuum: workers together with leader could overrun cost budget Chao Li

• Earlier messages
• Later messages