pgsql-hackers  

Messages by Thread

• • Re: Possible regression in PG18 beta1 Sadeq Dousti
  • Re: Possible regression in PG18 beta1 Sami Imseih
  • Re: Possible regression in PG18 beta1 Sadeq Dousti
  • Re: Possible regression in PG18 beta1 Sami Imseih
  • Re: Possible regression in PG18 beta1 Sadeq Dousti
  • Re: Possible regression in PG18 beta1 Maciek Sakrejda
  • Re: Possible regression in PG18 beta1 Peter Geoghegan
• Re: Add Option To Check All Addresses For Matching target_session_attr Andrew Jackson
• pg_upgrade ability to create extension from scripts Regina Obe
  • Re: pg_upgrade ability to create extension from scripts Andreas Karlsson
  • RE: pg_upgrade ability to create extension from scripts Regina Obe
  • Re: pg_upgrade ability to create extension from scripts Andreas Karlsson
• Foreign key isolation tests Paul A Jungwirth
• Proposal: Make cfbot fail on patches not created by "git format-patch" Jelte Fennema-Nio
  • Re: Proposal: Make cfbot fail on patches not created by "git format-patch" Daniel Gustafsson
  • Re: Proposal: Make cfbot fail on patches not created by "git format-patch" Jelte Fennema-Nio
  • Re: Proposal: Make cfbot fail on patches not created by "git format-patch" Aleksander Alekseev
  • Re: Proposal: Make cfbot fail on patches not created by "git format-patch" Jacob Champion
  • Re: Proposal: Make cfbot fail on patches not created by "git format-patch" Florents Tselai
  • Re: Proposal: Make cfbot fail on patches not created by "git format-patch" Tom Lane
  • Re: Proposal: Make cfbot fail on patches not created by "git format-patch" Jacob Champion
  • Re: Proposal: Make cfbot fail on patches not created by "git format-patch" Jelte Fennema-Nio
  • Re: Proposal: Make cfbot fail on patches not created by "git format-patch" Tom Lane
  • Re: Proposal: Make cfbot fail on patches not created by "git format-patch" Ashutosh Bapat
  • Re: Proposal: Make cfbot fail on patches not created by "git format-patch" David G. Johnston
• Make wal_receiver_timeout configurable per subscription Fujii Masao
  • Re: Make wal_receiver_timeout configurable per subscription Srinath Reddy Sadipiralla
  • Re: Make wal_receiver_timeout configurable per subscription Amit Kapila
  • Re: Make wal_receiver_timeout configurable per subscription Robert Haas
  • Re: Make wal_receiver_timeout configurable per subscription Michael Paquier
  • Re: Make wal_receiver_timeout configurable per subscription vignesh C
  • Re: Make wal_receiver_timeout configurable per subscription Masahiko Sawada
  • Re: Make wal_receiver_timeout configurable per subscription Fujii Masao
  • Re: Make wal_receiver_timeout configurable per subscription Amit Kapila
  • Re: Make wal_receiver_timeout configurable per subscription Fujii Masao
• Document default values for pgoutput options + fix missing initialization for "origin" Fujii Masao
  • Re: Document default values for pgoutput options + fix missing initialization for "origin" Euler Taveira
  • Re: Document default values for pgoutput options + fix missing initialization for "origin" Amit Kapila
  • Re: Document default values for pgoutput options + fix missing initialization for "origin" Fujii Masao
  • Re: Document default values for pgoutput options + fix missing initialization for "origin" Fujii Masao
• PG 17.2 compilation fails with -std=c11 on mac Lakshmi Narayana Velayudam
  • Re: PG 17.2 compilation fails with -std=c11 on mac Tom Lane
  • Re: PG 17.2 compilation fails with -std=c11 on mac Tom Lane
  • Re: PG 17.2 compilation fails with -std=c11 on mac Tom Lane
• C extension compilation failed while using PG 17.2 on mac m1 Lakshmi Narayana Velayudam
  • Re: C extension compilation failed while using PG 17.2 on mac m1 Tom Lane
• wrong query results on bf leafhopper Andres Freund
  • Re: wrong query results on bf leafhopper Alena Rybakina
  • Re: wrong query results on bf leafhopper Robins Tharakan
  • Re: wrong query results on bf leafhopper Andres Freund
  • Re: wrong query results on bf leafhopper David Rowley
  • Re: wrong query results on bf leafhopper Tom Lane
  • Re: wrong query results on bf leafhopper David Rowley
  • Re: wrong query results on bf leafhopper Tomas Vondra
  • Re: wrong query results on bf leafhopper Robins Tharakan
  • Re: wrong query results on bf leafhopper Tom Lane
  • Re: wrong query results on bf leafhopper Andres Freund
  • Re: wrong query results on bf leafhopper Robins Tharakan
• Align wording on copyright organization Daniel Gustafsson
  • Re: Align wording on copyright organization Dave Page
  • Re: Align wording on copyright organization Tom Lane
  • Re: Align wording on copyright organization Daniel Gustafsson
  • Re: Align wording on copyright organization Daniel Gustafsson
  • Re: Align wording on copyright organization Dave Page
• Re: Virtual generated columns Alexander Lakhin
  • Re: Virtual generated columns Richard Guo
  • Re: Virtual generated columns jian he
  • Re: Virtual generated columns Richard Guo
  • Re: Virtual generated columns jian he
• Binary operators for cubes Kirill Panin
• Add comment explaining why queryid is int64 in pg_stat_statements Shaik Mohammad Mujeeb
  • Re: Add comment explaining why queryid is int64 in pg_stat_statements Ilia Evdokimov
  • Re: Add comment explaining why queryid is int64 in pg_stat_statements Shaik Mohammad Mujeeb
  • Re: Add comment explaining why queryid is int64 in pg_stat_statements wenhui qiu
  • Re: Add comment explaining why queryid is int64 in pg_stat_statements Michael Paquier
  • Re: Add comment explaining why queryid is int64 in pg_stat_statements Shaik Mohammad Mujeeb
  • Re: Add comment explaining why queryid is int64 in pg_stat_statements Junwang Zhao
  • Re: Add comment explaining why queryid is int64 in pg_stat_statements Peter Eisentraut
  • Re: Add comment explaining why queryid is int64 in pg_stat_statements Sami Imseih
  • Re: Add comment explaining why queryid is int64 in pg_stat_statements David Rowley
  • Re: Add comment explaining why queryid is int64 in pg_stat_statements Michael Paquier
  • Re: Add comment explaining why queryid is int64 in pg_stat_statements Lukas Fittl
  • Re: Add comment explaining why queryid is int64 in pg_stat_statements Michael Paquier
  • Re: Add comment explaining why queryid is int64 in pg_stat_statements David Rowley
  • Re: Add comment explaining why queryid is int64 in pg_stat_statements Michael Paquier
  • Re: Add comment explaining why queryid is int64 in pg_stat_statements Sami Imseih
  • Re: Add comment explaining why queryid is int64 in pg_stat_statements Michael Paquier
  • Re: Add comment explaining why queryid is int64 in pg_stat_statements David Rowley
  • Re: Add comment explaining why queryid is int64 in pg_stat_statements Peter Eisentraut
  • Re: Add comment explaining why queryid is int64 in pg_stat_statements David Rowley
  • Re: Add comment explaining why queryid is int64 in pg_stat_statements Michael Paquier
  • Re: Add comment explaining why queryid is int64 in pg_stat_statements Michael Paquier
  • Re: Add comment explaining why queryid is int64 in pg_stat_statements Nathan Bossart
  • Re: Add comment explaining why queryid is int64 in pg_stat_statements Michael Paquier
  • Re: Add comment explaining why queryid is int64 in pg_stat_statements David Rowley
  • Re: Add comment explaining why queryid is int64 in pg_stat_statements David Rowley
  • Re: Add comment explaining why queryid is int64 in pg_stat_statements Shaik Mohammad Mujeeb
  • Re: Add comment explaining why queryid is int64 in pg_stat_statements Michael Paquier
  • Re: Add comment explaining why queryid is int64 in pg_stat_statements Julien Rouhaud
  • Re: Add comment explaining why queryid is int64 in pg_stat_statements David Rowley
  • Re: Add comment explaining why queryid is int64 in pg_stat_statements Michael Paquier
  • Re: Add comment explaining why queryid is int64 in pg_stat_statements Julien Rouhaud
• Re: Update LDAP Protocol in fe-connect.c to v3 Pavel Seleznev
  • Re: Update LDAP Protocol in fe-connect.c to v3 Peter Eisentraut
• Assertion failure in smgr.c when using pg_prewarm with partitioned tables Masahiro Ikeda
  • Re: Assertion failure in smgr.c when using pg_prewarm with partitioned tables Dilip Kumar
  • Re: Assertion failure in smgr.c when using pg_prewarm with partitioned tables Fujii Masao
  • Re: Assertion failure in smgr.c when using pg_prewarm with partitioned tables Dilip Kumar
  • Re: Assertion failure in smgr.c when using pg_prewarm with partitioned tables Richard Guo
  • Re: Assertion failure in smgr.c when using pg_prewarm with partitioned tables Masahiro Ikeda
  • Re: Assertion failure in smgr.c when using pg_prewarm with partitioned tables Dilip Kumar
  • Re: Assertion failure in smgr.c when using pg_prewarm with partitioned tables Fujii Masao
  • Re: Assertion failure in smgr.c when using pg_prewarm with partitioned tables Masahiro Ikeda
  • Re: Assertion failure in smgr.c when using pg_prewarm with partitioned tables Fujii Masao
  • Re: Assertion failure in smgr.c when using pg_prewarm with partitioned tables ikedamsh
  • Re: Assertion failure in smgr.c when using pg_prewarm with partitioned tables Fujii Masao
  • Re: Assertion failure in smgr.c when using pg_prewarm with partitioned tables Masahiro Ikeda
  • Re: Assertion failure in smgr.c when using pg_prewarm with partitioned tables Fujii Masao
  • Re: Assertion failure in smgr.c when using pg_prewarm with partitioned tables Masahiro Ikeda
• xlogrecovery.c:WaitForWALToBecomeAvailable() - make "switched WAL source" visible by default? Jakub Wartak
• [BUG] Skipped initialization of some xl_xact_parsed_prepare fields Daniil Davydov
  • Re: [BUG] Skipped initialization of some xl_xact_parsed_prepare fields Fujii Masao
  • Re: [BUG] Skipped initialization of some xl_xact_parsed_prepare fields Fujii Masao
  • Re: [BUG] Skipped initialization of some xl_xact_parsed_prepare fields Daniil Davydov
• 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
  • Re: Incremental Sort Cost Estimation Instability Alexander Korotkov
  • Re: Incremental Sort Cost Estimation Instability Alexander Korotkov
• 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 Scott Mead
  • Re: Disable parallel query by default Álvaro Herrera
• ARM/ARM64 SpinLockAcquire and SpinLockRelease are not full barriers Yura Sokolov
  • Re: 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: Memoize ANTI and SEMI JOIN inner Andres Freund
  • Re: Memoize ANTI and SEMI JOIN inner Richard Guo
• Re: Test mail for pgsql-hackers Andres Freund
• Re: Improve monitoring of shared memory allocations Amit Kapila
• 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 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
  • Re: fix: propagate M4 env variable to flex subprocess J. Javier Maestro
• 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: Adding error messages to a few slash commands Robin Haberkorn
• 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: Consider explicit incremental sort for Append and MergeAppend Richard Guo
• Re: Add SPLIT PARTITION/MERGE PARTITIONS commands Dmitry Koval
  • Re: Add SPLIT PARTITION/MERGE PARTITIONS commands jian he
  • Re: Add SPLIT PARTITION/MERGE PARTITIONS commands Dmitry Koval
  • Re: Add SPLIT PARTITION/MERGE PARTITIONS commands jian he
  • Re: Add SPLIT PARTITION/MERGE PARTITIONS commands Dmitry Koval

• Earlier messages
• Later messages