pgsql-hackers  

Messages by Thread

• Should we optimize the `ORDER BY random() LIMIT x` case? Aleksander Alekseev
  • Re: Should we optimize the `ORDER BY random() LIMIT x` case? wenhui qiu
  • Re: Should we optimize the `ORDER BY random() LIMIT x` case? Andrei Lepikhov
  • Re: Should we optimize the `ORDER BY random() LIMIT x` case? Aleksander Alekseev
  • Re: Should we optimize the `ORDER BY random() LIMIT x` case? Andrei Lepikhov
  • Re: Should we optimize the `ORDER BY random() LIMIT x` case? Aleksander Alekseev
  • Re: Should we optimize the `ORDER BY random() LIMIT x` case? Tom Lane
  • Re: Should we optimize the `ORDER BY random() LIMIT x` case? Vik Fearing
  • Re: Should we optimize the `ORDER BY random() LIMIT x` case? Tom Lane
  • Re: Should we optimize the `ORDER BY random() LIMIT x` case? Vik Fearing
  • Re: Should we optimize the `ORDER BY random() LIMIT x` case? Nico Williams
  • Re: Should we optimize the `ORDER BY random() LIMIT x` case? Nico Williams
  • Re: Should we optimize the `ORDER BY random() LIMIT x` case? Nico Williams
  • Re: Should we optimize the `ORDER BY random() LIMIT x` case? Aleksander Alekseev
  • Re: Should we optimize the `ORDER BY random() LIMIT x` case? Nico Williams
  • Re: Should we optimize the `ORDER BY random() LIMIT x` case? Nico Williams
  • Re: Should we optimize the `ORDER BY random() LIMIT x` case? Aleksander Alekseev
  • Re: Should we optimize the `ORDER BY random() LIMIT x` case? Andrei Lepikhov
  • Re: Should we optimize the `ORDER BY random() LIMIT x` case? Aleksander Alekseev
  • Re: Should we optimize the `ORDER BY random() LIMIT x` case? Vik Fearing
• PostgreSQL 18 Beta 1 io_max_concurrency Jafri, Nazneen
  • Re: PostgreSQL 18 Beta 1 io_max_concurrency Tom Lane
• Re: Incremental Sort Cost Estimation Instability Andrei Lepikhov
• vectorized CRC on ARM64 John Naylor
• Disable parallel query by default Scott Mead
  • Re: Disable parallel query by default Lukas Fittl
  • Re: Disable parallel query by default Greg Sabino Mullane
  • Re: Disable parallel query by default Scott Mead
  • Re: Disable parallel query by default Laurenz Albe
  • Re: Disable parallel query by default Scott Mead
  • Re: Disable parallel query by default Laurenz Albe
  • Re: Disable parallel query by default Álvaro Herrera
• ARM/ARM64 SpinLockAcquire and SpinLockRelease are not full barriers Yura Sokolov
• spurious pg_amcheck test failure Andres Freund
• Re: Serverside SNI support in libpq Andres Freund
• Re: Test mail for pgsql-hackers Andres Freund
• Backward movement of confirmed_flush resulting in data duplication. shveta malik
  • Re: Backward movement of confirmed_flush resulting in data duplication. Dilip Kumar
  • Re: Backward movement of confirmed_flush resulting in data duplication. Amit Kapila
  • Re: Backward movement of confirmed_flush resulting in data duplication. Dilip Kumar
  • Re: Backward movement of confirmed_flush resulting in data duplication. Alexander Kukushkin
  • Re: Backward movement of confirmed_flush resulting in data duplication. Amit Kapila
  • Re: Backward movement of confirmed_flush resulting in data duplication. Dilip Kumar
  • Re: Backward movement of confirmed_flush resulting in data duplication. Nisha Moond
  • Re: Backward movement of confirmed_flush resulting in data duplication. Amit Kapila
• Add explicit initialization for all PlannerGlobal fields Richard Guo
  • Re: Add explicit initialization for all PlannerGlobal fields David Rowley
  • Re: Add explicit initialization for all PlannerGlobal fields Richard Guo
• fix: propagate M4 env variable to flex subprocess J. Javier Maestro
  • Re: fix: propagate M4 env variable to flex subprocess Andres Freund
  • Re: fix: propagate M4 env variable to flex subprocess J. Javier Maestro
  • Re: fix: propagate M4 env variable to flex subprocess Nazir Bilal Yavuz
• make VALIDATE domain constraint lock on related relations as ShareUpdateExclusiveLock jian he
  • Re: make VALIDATE domain constraint lock on related relations as ShareUpdateExclusiveLock Dilip Kumar
  • Re: make VALIDATE domain constraint lock on related relations as ShareUpdateExclusiveLock wenhui qiu
• Re: INSERT ... ON CONFLICT DO SELECT [FOR ...] take 2 Andreas Karlsson
• Consider explicit incremental sort for Append and MergeAppend Richard Guo
  • Re: Consider explicit incremental sort for Append and MergeAppend Andrei Lepikhov
  • Re: Consider explicit incremental sort for Append and MergeAppend Robert Haas
• Re: Add SPLIT PARTITION/MERGE PARTITIONS commands Dmitry Koval
  • Re: Add SPLIT PARTITION/MERGE PARTITIONS commands jian he
• Re: FileFallocate misbehaving on XFS Pierre Barre
• Proposal: Exploring LSM Tree‑Based Storage Engine for PostgreSQL (Inspired by MyRocks) Manish Rai Jain
  • Re: Proposal: Exploring LSM Tree‑Based Storage Engine for PostgreSQL (Inspired by MyRocks) Matthias van de Meent
  • Re: Proposal: Exploring LSM Tree‑Based Storage Engine for PostgreSQL (Inspired by MyRocks) Aleksander Alekseev
  • Re: Proposal: Exploring LSM Tree‑Based Storage Engine for PostgreSQL (Inspired by MyRocks) Nico Williams
• Re: Trivial comment fix for tsquerysend() Álvaro Herrera
• Request for Implementation of Custom Error Messages for CHECK Constraints Miguel Ferreira
  • Re: Request for Implementation of Custom Error Messages for CHECK Constraints Tom Lane
  • RE: Request for Implementation of Custom Error Messages for CHECK Constraints Miguel Ferreira
  • Re: Request for Implementation of Custom Error Messages for CHECK Constraints Bruce Momjian
  • Re: Request for Implementation of Custom Error Messages for CHECK Constraints David G. Johnston
  • Re: Request for Implementation of Custom Error Messages for CHECK Constraints Bruce Momjian
  • Re: Request for Implementation of Custom Error Messages for CHECK Constraints David G. Johnston
  • RE: Request for Implementation of Custom Error Messages for CHECK Constraints Miguel Ferreira
  • Re: Request for Implementation of Custom Error Messages for CHECK Constraints Marcos Pegoraro
• Re: Inval reliability, especially for inplace updates Noah Misch
• Suggestion to add --continue-client-on-abort option to pgbench ikedarintarof
  • Re: Suggestion to add --continue-client-on-abort option to pgbench Stepan Neretin
  • Re: Suggestion to add --continue-client-on-abort option to pgbench Matthias van de Meent
  • Re: Suggestion to add --continue-client-on-abort option to pgbench Stepan Neretin
  • Re: Suggestion to add --continue-client-on-abort option to pgbench Rintaro.Ikeda
  • Re: Suggestion to add --continue-client-on-abort option to pgbench Dilip Kumar
  • Re: Suggestion to add --continue-client-on-abort option to pgbench Srinath Reddy Sadipiralla
• is there any query that can cover these statements in join_is_legal()? g l
• Re: PATCH: jsonpath string methods: lower, upper, initcap, l/r/btrim, replace, split_part Robert Haas
  • Re: PATCH: jsonpath string methods: lower, upper, initcap, l/r/btrim, replace, split_part David E. Wheeler
  • Re: PATCH: jsonpath string methods: lower, upper, initcap, l/r/btrim, replace, split_part Florents Tselai
  • Re: PATCH: jsonpath string methods: lower, upper, initcap, l/r/btrim, replace, split_part David E. Wheeler
  • Re: PATCH: jsonpath string methods: lower, upper, initcap, l/r/btrim, replace, split_part Florents Tselai
• Re: SQL:2011 application time Robert Haas
• Fix incorrect order of params in comment Daniel Gustafsson
  • Re: Fix incorrect order of params in comment Michael Paquier
  • Re: Fix incorrect order of params in comment Daniel Gustafsson
• Re: Useless LEFT JOIN breaks MIN/MAX optimization Robert Haas
  • Re: Useless LEFT JOIN breaks MIN/MAX optimization Alena Rybakina
  • Re: Useless LEFT JOIN breaks MIN/MAX optimization Tom Lane
  • Re: Useless LEFT JOIN breaks MIN/MAX optimization Alena Rybakina
• Re: Amcheck verification of GiST and GIN Arseniy Mukhin
  • Re: Amcheck verification of GiST and GIN Tomas Vondra
• strange perf regression with data checksums Tomas Vondra
  • Re: strange perf regression with data checksums Aleksander Alekseev
  • Re: strange perf regression with data checksums Tomas Vondra
  • Re: strange perf regression with data checksums Aleksander Alekseev
  • Re: strange perf regression with data checksums Tomas Vondra
  • Re: strange perf regression with data checksums Andres Freund
  • Re: strange perf regression with data checksums Peter Geoghegan
  • Re: strange perf regression with data checksums Peter Geoghegan
  • Re: strange perf regression with data checksums Peter Geoghegan
  • Re: strange perf regression with data checksums Tomas Vondra
  • Re: strange perf regression with data checksums Peter Geoghegan
  • Re: strange perf regression with data checksums Peter Geoghegan
  • Re: strange perf regression with data checksums Tomas Vondra
  • Re: strange perf regression with data checksums Peter Geoghegan
  • Re: strange perf regression with data checksums Tomas Vondra
  • Re: strange perf regression with data checksums Peter Geoghegan
  • Re: strange perf regression with data checksums Peter Geoghegan
• Re: [PATCH] avoid double scanning in function byteain Stepan Neretin
  • Re: [PATCH] avoid double scanning in function byteain Stepan Neretin
  • Re: [PATCH] avoid double scanning in function byteain Stepan Neretin
  • Re: [PATCH] avoid double scanning in function byteain Aleksander Alekseev
  • Re: [PATCH] avoid double scanning in function byteain Stepan Neretin
• Re: Issues with 2PC at recovery: CLOG lookups and GlobalTransactionData Michael Paquier
• Why our Valgrind reports suck Tom Lane
  • Re: Why our Valgrind reports suck Yasir
  • Re: Why our Valgrind reports suck Andres Freund
  • Re: Why our Valgrind reports suck Andres Freund
  • Re: Why our Valgrind reports suck Tom Lane
  • Re: Why our Valgrind reports suck Tom Lane
  • Re: Why our Valgrind reports suck Tom Lane
  • Re: Why our Valgrind reports suck Tom Lane
  • Re: Why our Valgrind reports suck Tom Lane
  • Re: Why our Valgrind reports suck Álvaro Herrera
  • Re: Why our Valgrind reports suck Tom Lane
  • Re: Why our Valgrind reports suck Yasir
• Fix PQport to never return NULL if the connection is valid Daniele Varrazzo
  • Re: Fix PQport to never return NULL if the connection is valid Daniele Varrazzo
  • Re: Fix PQport to never return NULL if the connection is valid Daniele Varrazzo
• Re: Valgrind - showing memory leaks Álvaro Herrera
  • Re: Valgrind - showing memory leaks Yasir
  • Re: Valgrind - showing memory leaks Tom Lane
  • Re: Valgrind - showing memory leaks Yasir
  • Re: Valgrind - showing memory leaks Álvaro Herrera
  • Re: Valgrind - showing memory leaks Tom Lane
  • Re: Valgrind - showing memory leaks Álvaro Herrera
  • Re: Valgrind - showing memory leaks Tom Lane
• Re: Valgrind - showing memory leaks? Aleksander Alekseev
• [PATCH] Fix <literal> tags in func.sgml Noboru Saito
  • Re: [PATCH] Fix <literal> tags in func.sgml Daniel Gustafsson
  • Re: [PATCH] Fix <literal> tags in func.sgml Tatsuo Ishii
  • Re: [PATCH] Fix <literal> tags in func.sgml Noboru Saito
  • Re: [PATCH] Fix <literal> tags in func.sgml Tatsuo Ishii
  • Re: [PATCH] Fix <literal> tags in func.sgml Michael Paquier
• Re: Proposal for enabling auto-vectorization for checksum calculations Matthew Sterrett
  • Re: Proposal for enabling auto-vectorization for checksum calculations Stepan Neretin
  • Re: Proposal for enabling auto-vectorization for checksum calculations Stepan Neretin
  • Re: Proposal for enabling auto-vectorization for checksum calculations Matthew Sterrett
  • Re: Proposal for enabling auto-vectorization for checksum calculations Nazir Bilal Yavuz
• Improve docs for n_distinct_inherited David Rowley
  • Re: Improve docs for n_distinct_inherited David G. Johnston
  • Re: Improve docs for n_distinct_inherited David Rowley
  • Re: Improve docs for n_distinct_inherited David G. Johnston
• Re: Limiting overshoot in nbtree's parallel SAOP index scans Matthias van de Meent
  • Re: Limiting overshoot in nbtree's parallel SAOP index scans Amit Kapila
• [PATCH] oauth: Prevent stack overflow by limiting JSON parse depth Jacob Champion
  • Re: [PATCH] oauth: Prevent stack overflow by limiting JSON parse depth Aleksander Alekseev
  • Re: [PATCH] oauth: Prevent stack overflow by limiting JSON parse depth Jacob Champion
• [PATCH] Fix missing comma in Requires.private with a Make macro Jacob Champion
  • Re: [PATCH] Fix missing comma in Requires.private with a Make macro Fabrízio de Royes Mello
  • Re: [PATCH] Fix missing comma in Requires.private with a Make macro Jacob Champion
  • Re: [PATCH] Fix missing comma in Requires.private with a Make macro Tom Lane
  • Re: [PATCH] Fix missing comma in Requires.private with a Make macro Álvaro Herrera
  • Re: [PATCH] Fix missing comma in Requires.private with a Make macro Jacob Champion
  • Re: [PATCH] Fix missing comma in Requires.private with a Make macro Tom Lane
  • Re: [PATCH] Fix missing comma in Requires.private with a Make macro Jacob Champion
  • libcurl in libpq.pc Christoph Berg
  • Re: libcurl in libpq.pc Jacob Champion
  • Re: libcurl in libpq.pc Jacob Champion
• Review/Pull Request: Adding new CRC32C implementation for IBM S390X Eduard Stefes
  • Re: Review/Pull Request: Adding new CRC32C implementation for IBM S390X Aleksander Alekseev
  • Re: Review/Pull Request: Adding new CRC32C implementation for IBM S390X John Naylor
  • Re: Review/Pull Request: Adding new CRC32C implementation for IBM S390X John Naylor
  • Re: Review/Pull Request: Adding new CRC32C implementation for IBM S390X Tom Lane
• pg_dump does not dump domain not-null constraint's comments jian he
  • Re: pg_dump does not dump domain not-null constraint's comments Álvaro Herrera
  • Re: pg_dump does not dump domain not-null constraint's comments jian he
  • Re: pg_dump does not dump domain not-null constraint's comments Álvaro Herrera
  • Re: pg_dump does not dump domain not-null constraint's comments jian he
• Improve tab completion for COPY torikoshia
  • Re: Improve tab completion for COPY Yugo Nagata
  • Re: Improve tab completion for COPY Masahiko Sawada
  • Re: Improve tab completion for COPY Yugo Nagata
  • Re: Improve tab completion for COPY torikoshia
• Incorrect calculation of path fraction value in MergeAppend Andrei Lepikhov
  • Re: Incorrect calculation of path fraction value in MergeAppend Álvaro Herrera
  • Re: Incorrect calculation of path fraction value in MergeAppend Andrei Lepikhov
  • Re: Incorrect calculation of path fraction value in MergeAppend Álvaro Herrera
  • Re: Incorrect calculation of path fraction value in MergeAppend Andrei Lepikhov
  • Re: Incorrect calculation of path fraction value in MergeAppend Álvaro Herrera
  • Re: Incorrect calculation of path fraction value in MergeAppend Tom Lane

• Earlier messages
• Later messages