pgsql-hackers  

Messages by Thread

• • Re: I/O worker and ConfigReload Dmitry Dolgov
• [PATCH] Extending FK check skipping on replicas to ADD FK and TRUNCATE Hannu Krosing
  • Re: [PATCH] Extending FK check skipping on replicas to ADD FK and TRUNCATE Hannu Krosing
• Please update your contact list: It must be pgsql-hackers@lists.postgresql.org * Neustradamus *
  • Re: Please update your contact list: It must be pgsql-hackers@lists.postgresql.org * Neustradamus *
• Testing PostgreSQL 18 beta ... André Verwijs
• Copy Tuple Desc in internal_get_result_type Lakshmi Narayana Velayudam
• Re: Covering the comparison between date and timestamp, tz, type Rustam ALLAKOV
• Re: Non-reproducible AIO failure Alexander Lakhin
  • Re: Non-reproducible AIO failure Tom Lane
  • Re: Non-reproducible AIO failure Thomas Munro
  • Re: Non-reproducible AIO failure Alexander Lakhin
  • Re: Non-reproducible AIO failure Thomas Munro
  • Re: Non-reproducible AIO failure Tom Lane
  • Re: Non-reproducible AIO failure Thomas Munro
  • Re: Non-reproducible AIO failure Tom Lane
  • Re: Non-reproducible AIO failure Thomas Munro
  • Re: Non-reproducible AIO failure Tom Lane
  • Re: Non-reproducible AIO failure Andres Freund
  • Re: Non-reproducible AIO failure Tom Lane
  • Re: Non-reproducible AIO failure Andres Freund
  • Re: Non-reproducible AIO failure Tom Lane
  • Re: Non-reproducible AIO failure Andres Freund
  • Re: Non-reproducible AIO failure Tom Lane
  • Re: Non-reproducible AIO failure Alexander Lakhin
  • Re: Non-reproducible AIO failure Tom Lane
  • Re: Non-reproducible AIO failure Robert Haas
  • Re: Non-reproducible AIO failure Alexander Lakhin
  • Re: Non-reproducible AIO failure Alexander Lakhin
  • Re: Non-reproducible AIO failure Alexander Lakhin
  • Re: Non-reproducible AIO failure Andres Freund
  • Re: Non-reproducible AIO failure Thomas Munro
  • Re: Non-reproducible AIO failure Alexander Lakhin
  • Re: Non-reproducible AIO failure Matthias van de Meent
  • Re: Non-reproducible AIO failure Tom Lane
  • Re: Non-reproducible AIO failure Konstantin Knizhnik
  • Re: Non-reproducible AIO failure Alexander Lakhin
  • Re: Non-reproducible AIO failure Konstantin Knizhnik
  • Re: Non-reproducible AIO failure Andres Freund
  • Re: Non-reproducible AIO failure Konstantin Knizhnik
  • Re: Non-reproducible AIO failure Thomas Munro
  • Re: Non-reproducible AIO failure Konstantin Knizhnik
  • Re: Non-reproducible AIO failure Andres Freund
  • Re: Non-reproducible AIO failure Konstantin Knizhnik
  • Re: Non-reproducible AIO failure Andres Freund
  • Re: Non-reproducible AIO failure Konstantin Knizhnik
  • Re: Non-reproducible AIO failure Konstantin Knizhnik
  • Re: Non-reproducible AIO failure Andres Freund
  • Re: Non-reproducible AIO failure Konstantin Knizhnik
  • Re: Non-reproducible AIO failure Andres Freund
  • Re: Non-reproducible AIO failure Konstantin Knizhnik
  • Re: Non-reproducible AIO failure Andres Freund
  • Re: Non-reproducible AIO failure Andres Freund
  • Re: Non-reproducible AIO failure Tom Lane
  • Re: Non-reproducible AIO failure Andres Freund
  • Re: Non-reproducible AIO failure Alexander Lakhin
  • Re: Non-reproducible AIO failure Nico Williams
  • Re: Non-reproducible AIO failure Andres Freund
  • Re: Non-reproducible AIO failure Tom Lane
  • Re: Non-reproducible AIO failure Konstantin Knizhnik
  • Re: Non-reproducible AIO failure Tomas Vondra
  • Re: Non-reproducible AIO failure Alexander Lakhin
• Fixing memory leaks in postgres_fdw Tom Lane
  • Re: Fixing memory leaks in postgres_fdw Etsuro Fujita
  • Re: Fixing memory leaks in postgres_fdw Tom Lane
  • Re: Fixing memory leaks in postgres_fdw Tom Lane
  • Re: Fixing memory leaks in postgres_fdw Tom Lane
  • Re: Fixing memory leaks in postgres_fdw Matheus Alcantara
  • Re: Fixing memory leaks in postgres_fdw Tom Lane
  • Re: Fixing memory leaks in postgres_fdw Tom Lane
  • Re: Fixing memory leaks in postgres_fdw Matheus Alcantara
  • Re: Fixing memory leaks in postgres_fdw Tom Lane
  • Re: Fixing memory leaks in postgres_fdw Tom Lane
  • Re: Fixing memory leaks in postgres_fdw Tom Lane
  • Re: Fixing memory leaks in postgres_fdw Matheus Alcantara
  • Re: Fixing memory leaks in postgres_fdw Tom Lane
  • Re: Fixing memory leaks in postgres_fdw Etsuro Fujita
• tighten generic_option_name, or store more carefully in catalog? Chapman Flack
  • Re: tighten generic_option_name, or store more carefully in catalog? Tom Lane
  • Re: tighten generic_option_name, or store more carefully in catalog? Chapman Flack
  • Re: tighten generic_option_name, or store more carefully in catalog? Tom Lane
  • Re: tighten generic_option_name, or store more carefully in catalog? Chapman Flack
  • Re: tighten generic_option_name, or store more carefully in catalog? Tom Lane
  • Re: tighten generic_option_name, or store more carefully in catalog? Chapman Flack
  • Re: tighten generic_option_name, or store more carefully in catalog? Tom Lane
• Add CHECK_FOR_INTERRUPTS in polling loop code path in XactLockTableWait Kevin K Biju
  • Re: Add CHECK_FOR_INTERRUPTS in polling loop code path in XactLockTableWait Fujii Masao
  • Re: Add CHECK_FOR_INTERRUPTS in polling loop code path in XactLockTableWait Kevin K Biju
  • Re: Add CHECK_FOR_INTERRUPTS in polling loop code path in XactLockTableWait Fujii Masao
  • Re: Add CHECK_FOR_INTERRUPTS in polling loop code path in XactLockTableWait Kevin K Biju
  • Re: Add CHECK_FOR_INTERRUPTS in polling loop code path in XactLockTableWait Fujii Masao
  • Re: Add CHECK_FOR_INTERRUPTS in polling loop code path in XactLockTableWait Xuneng Zhou
  • Re: Add CHECK_FOR_INTERRUPTS in polling loop code path in XactLockTableWait Xuneng Zhou
  • Re: Add CHECK_FOR_INTERRUPTS in polling loop code path in XactLockTableWait Fujii Masao
  • Re: Add CHECK_FOR_INTERRUPTS in polling loop code path in XactLockTableWait Xuneng Zhou
  • Re: Add CHECK_FOR_INTERRUPTS in polling loop code path in XactLockTableWait Xuneng Zhou
  • Re: Add CHECK_FOR_INTERRUPTS in polling loop code path in XactLockTableWait Xuneng Zhou
• mention unused_oids script in pg_proc.dat Florents Tselai
  • Re: mention unused_oids script in pg_proc.dat Michael Paquier
  • Re: mention unused_oids script in pg_proc.dat Florents Tselai
  • Re: mention unused_oids script in pg_proc.dat Álvaro Herrera
  • Re: mention unused_oids script in pg_proc.dat Florents Tselai
• Random subscription 021_twophase test failure on kestrel vignesh C
  • Re: Random subscription 021_twophase test failure on kestrel Michael Paquier
  • Re: Random subscription 021_twophase test failure on kestrel Amit Kapila
  • Re: Random subscription 021_twophase test failure on kestrel Michael Paquier
  • Re: Random subscription 021_twophase test failure on kestrel vignesh C
• Disallow concurrent ALTER DOMAIN and DROP DOMAIN jian he
• pg18: Virtual generated columns are not (yet) safe when superuser selects from them Feike Steenbergen
  • Re: pg18: Virtual generated columns are not (yet) safe when superuser selects from them jian he
  • Re: pg18: Virtual generated columns are not (yet) safe when superuser selects from them Feike Steenbergen
  • Re: pg18: Virtual generated columns are not (yet) safe when superuser selects from them jian he
  • Re: pg18: Virtual generated columns are not (yet) safe when superuser selects from them David G. Johnston
  • Re: pg18: Virtual generated columns are not (yet) safe when superuser selects from them Feike Steenbergen
  • Re: pg18: Virtual generated columns are not (yet) safe when superuser selects from them jian he
  • Re: pg18: Virtual generated columns are not (yet) safe when superuser selects from them Feike Steenbergen
  • Re: pg18: Virtual generated columns are not (yet) safe when superuser selects from them Robert Haas
  • Re: pg18: Virtual generated columns are not (yet) safe when superuser selects from them David G. Johnston
  • Re: pg18: Virtual generated columns are not (yet) safe when superuser selects from them Tom Lane
  • Re: pg18: Virtual generated columns are not (yet) safe when superuser selects from them Jeff Davis
  • Re: pg18: Virtual generated columns are not (yet) safe when superuser selects from them Tom Lane
  • Re: pg18: Virtual generated columns are not (yet) safe when superuser selects from them Jeff Davis
  • Re: pg18: Virtual generated columns are not (yet) safe when superuser selects from them jian he
  • Re: pg18: Virtual generated columns are not (yet) safe when superuser selects from them Isaac Morland
  • Re: pg18: Virtual generated columns are not (yet) safe when superuser selects from them Tom Lane
  • Re: pg18: Virtual generated columns are not (yet) safe when superuser selects from them Robert Haas
  • Re: pg18: Virtual generated columns are not (yet) safe when superuser selects from them Bruce Momjian
  • Re: pg18: Virtual generated columns are not (yet) safe when superuser selects from them Robert Haas
  • Re: pg18: Virtual generated columns are not (yet) safe when superuser selects from them Jeff Davis
  • Re: pg18: Virtual generated columns are not (yet) safe when superuser selects from them Isaac Morland
  • Re: pg18: Virtual generated columns are not (yet) safe when superuser selects from them Feike Steenbergen
  • Re: pg18: Virtual generated columns are not (yet) safe when superuser selects from them Tom Lane
  • Re: pg18: Virtual generated columns are not (yet) safe when superuser selects from them Bruce Momjian
  • Re: pg18: Virtual generated columns are not (yet) safe when superuser selects from them Matthias van de Meent
  • Re: pg18: Virtual generated columns are not (yet) safe when superuser selects from them Tom Lane
  • Re: pg18: Virtual generated columns are not (yet) safe when superuser selects from them Matthias van de Meent
  • Re: pg18: Virtual generated columns are not (yet) safe when superuser selects from them Peter Eisentraut
  • Re: pg18: Virtual generated columns are not (yet) safe when superuser selects from them Pavel Stehule
  • Re: pg18: Virtual generated columns are not (yet) safe when superuser selects from them Feike Steenbergen
  • Re: pg18: Virtual generated columns are not (yet) safe when superuser selects from them Amit Kapila
  • Re: pg18: Virtual generated columns are not (yet) safe when superuser selects from them Robert Haas
  • Re: pg18: Virtual generated columns are not (yet) safe when superuser selects from them jian he
  • Re: pg18: Virtual generated columns are not (yet) safe when superuser selects from them Robert Haas
  • Re: pg18: Virtual generated columns are not (yet) safe when superuser selects from them Christoph Berg
  • Re: pg18: Virtual generated columns are not (yet) safe when superuser selects from them Tom Lane
  • Re: pg18: Virtual generated columns are not (yet) safe when superuser selects from them Christoph Berg
• Re: XMLSerialize: version and explicit XML declaration Jim Jones
• Replication slot is not able to sync up Suraj Kharage
  • Re: Replication slot is not able to sync up Amit Kapila
  • Re: Replication slot is not able to sync up Robert Haas
  • Re: Replication slot is not able to sync up Amit Kapila
  • Re: Replication slot is not able to sync up shveta malik
  • Re: Replication slot is not able to sync up shveta malik
  • Re: Replication slot is not able to sync up Masahiko Sawada
  • RE: Replication slot is not able to sync up Zhijie Hou (Fujitsu)
  • Re: Replication slot is not able to sync up Masahiko Sawada
  • Re: Replication slot is not able to sync up shveta malik
  • Re: Replication slot is not able to sync up Amit Kapila
  • RE: Replication slot is not able to sync up Zhijie Hou (Fujitsu)
  • Re: Replication slot is not able to sync up shveta malik
  • Re: Replication slot is not able to sync up Amit Kapila
  • Re: Replication slot is not able to sync up Peter Smith
  • Re: Replication slot is not able to sync up shveta malik
  • Re: Replication slot is not able to sync up Robert Haas
  • Re: Replication slot is not able to sync up Amit Kapila
  • RE: Replication slot is not able to sync up Zhijie Hou (Fujitsu)
  • Re: Replication slot is not able to sync up Amul Sul
  • Re: Replication slot is not able to sync up Amit Kapila
  • Re: Replication slot is not able to sync up Amul Sul
  • Re: Replication slot is not able to sync up Robert Haas
  • Logical Replication slot disappeared after promote Standby Perumal Raj
  • RE: Logical Replication slot disappeared after promote Standby Zhijie Hou (Fujitsu)
  • Re: Logical Replication slot disappeared after promote Standby Perumal Raj
  • Re: Logical Replication slot disappeared after promote Standby shveta malik
  • Re: Logical Replication slot disappeared after promote Standby Perumal Raj
• Understanding when VM record needs snapshot conflict horizon Melanie Plageman
  • Re: Understanding when VM record needs snapshot conflict horizon Andres Freund
  • Re: Understanding when VM record needs snapshot conflict horizon Melanie Plageman
  • Re: Understanding when VM record needs snapshot conflict horizon Dilip Kumar
  • Re: Understanding when VM record needs snapshot conflict horizon Melanie Plageman
• Re: Tree-walker callbacks vs -Wdeprecated-non-prototype Andres Freund
• Relstats after VACUUM FULL and CLUSTER Erik Nordström
  • Re: Relstats after VACUUM FULL and CLUSTER Sami Imseih
  • Re: Relstats after VACUUM FULL and CLUSTER Erik Nordström
  • Re: Relstats after VACUUM FULL and CLUSTER Sami Imseih
  • Re: Relstats after VACUUM FULL and CLUSTER Sami Imseih
  • Re: Relstats after VACUUM FULL and CLUSTER Erik Nordström
  • Re: Relstats after VACUUM FULL and CLUSTER Sami Imseih
• Expression push down from Join Node to below node. Shubhankar Anand Kulkarni
  • Re: Expression push down from Join Node to below node. Andy Fan
  • Re: Expression push down from Join Node to below node. Shubhankar Anand Kulkarni
  • Re: Expression push down from Join Node to below node. Shubhankar Anand Kulkarni
  • Re: Expression push down from Join Node to below node. Andy Fan
• Pathify RHS unique-ification for semijoin planning Richard Guo
  • Re: Pathify RHS unique-ification for semijoin planning Andy Fan
  • Re: Pathify RHS unique-ification for semijoin planning wenhui qiu
  • Re: Pathify RHS unique-ification for semijoin planning Richard Guo
• Feature Suggestion: Make synchronous_commit a table level property Anas-ur-Rasheed Khan
  • Re: Feature Suggestion: Make synchronous_commit a table level property Andy Fan
  • Re: Feature Suggestion: Make synchronous_commit a table level property Christoph Moench-Tegeder

• Earlier messages
• Later messages