pgsql-hackers  

Messages by Thread

• • Re: Amcheck verification of GiST and GIN Arseniy Mukhin
  • Re: Amcheck verification of GiST and GIN Andrey Borodin
  • Re: Amcheck verification of GiST and GIN Arseniy Mukhin
  • Re: Amcheck verification of GiST and GIN Tomas Vondra
  • Re: Amcheck verification of GiST and GIN Arseniy Mukhin
  • Re: Amcheck verification of GiST and GIN Tomas Vondra
  • Re: Amcheck verification of GiST and GIN Thom Brown
  • Re: Amcheck verification of GiST and GIN Tomas Vondra
• 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: 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 jian he
  • 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 Peter Eisentraut
  • 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 Peter Eisentraut
  • Re: pg18: Virtual generated columns are not (yet) safe when superuser selects from them Peter Eisentraut
• Re: Random subscription 021_twophase test failure on kestrel Michael Paquier
  • Re: Random subscription 021_twophase test failure on kestrel vignesh C
• 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
  • Re: Assertion failure in smgr.c when using pg_prewarm with partitioned tables Fujii Masao
• Add AioUringCompletion in wait_event_names.txt and a safeguard in generate-wait_event_types.pl Bertrand Drouvot
  • Re: Add AioUringCompletion in wait_event_names.txt and a safeguard in generate-wait_event_types.pl Michael Paquier
  • Re: Add AioUringCompletion in wait_event_names.txt and a safeguard in generate-wait_event_types.pl Michael Paquier
  • Re: Add AioUringCompletion in wait_event_names.txt and a safeguard in generate-wait_event_types.pl Bertrand Drouvot
• Re: Persist injection points across server restarts Rahila Syed
  • Re: Persist injection points across server restarts Michael Paquier
  • Re: Persist injection points across server restarts Rahila Syed
  • Re: Persist injection points across server restarts Michael Paquier
  • Re: Persist injection points across server restarts Rahila Syed
  • Re: Persist injection points across server restarts Andrey Borodin
  • Re: Persist injection points across server restarts Jeff Davis
  • Re: Persist injection points across server restarts Michael Paquier
  • Re: Persist injection points across server restarts Jeff Davis
  • Re: Persist injection points across server restarts Andres Freund
  • Re: Persist injection points across server restarts Michael Paquier
  • Re: Persist injection points across server restarts Michael Paquier
• Re: Slot's restart_lsn may point to removed WAL segment after hard restart unexpectedly Amit Kapila
  • Re: Slot's restart_lsn may point to removed WAL segment after hard restart unexpectedly Vitaly Davydov
  • Re: Slot's restart_lsn may point to removed WAL segment after hard restart unexpectedly Amit Kapila
  • Re: Slot's restart_lsn may point to removed WAL segment after hard restart unexpectedly Vitaly Davydov
  • Re: Slot's restart_lsn may point to removed WAL segment after hard restart unexpectedly Alexander Korotkov
  • Re: Slot's restart_lsn may point to removed WAL segment after hard restart unexpectedly Amit Kapila
  • Re: Slot's restart_lsn may point to removed WAL segment after hard restart unexpectedly Alexander Korotkov
  • Re: Slot's restart_lsn may point to removed WAL segment after hard restart unexpectedly Alexander Korotkov
  • Re: Slot's restart_lsn may point to removed WAL segment after hard restart unexpectedly Amit Kapila
  • Re: Slot's restart_lsn may point to removed WAL segment after hard restart unexpectedly Alexander Korotkov
  • Re: Slot's restart_lsn may point to removed WAL segment after hard restart unexpectedly Amit Kapila
  • Re: Slot's restart_lsn may point to removed WAL segment after hard restart unexpectedly Alexander Korotkov
  • Re: Slot's restart_lsn may point to removed WAL segment after hard restart unexpectedly Vitaly Davydov
  • Re: Slot's restart_lsn may point to removed WAL segment after hard restart unexpectedly Amit Kapila
  • Re: Slot's restart_lsn may point to removed WAL segment after hard restart unexpectedly Vitaly Davydov
  • Re: Slot's restart_lsn may point to removed WAL segment after hard restart unexpectedly Alexander Korotkov
  • Re: Slot's restart_lsn may point to removed WAL segment after hard restart unexpectedly Amit Kapila
  • Re: Slot's restart_lsn may point to removed WAL segment after hard restart unexpectedly Alexander Lakhin
  • Re: Slot's restart_lsn may point to removed WAL segment after hard restart unexpectedly Alexander Korotkov
  • Re: Slot's restart_lsn may point to removed WAL segment after hard restart unexpectedly Alexander Korotkov
  • Re: Slot's restart_lsn may point to removed WAL segment after hard restart unexpectedly Alexander Lakhin
  • Re: Slot's restart_lsn may point to removed WAL segment after hard restart unexpectedly Tom Lane
  • Re: Slot's restart_lsn may point to removed WAL segment after hard restart unexpectedly Alexander Korotkov
  • RE: Slot's restart_lsn may point to removed WAL segment after hard restart unexpectedly Hayato Kuroda (Fujitsu)
  • Re: Slot's restart_lsn may point to removed WAL segment after hard restart unexpectedly Alexander Korotkov
  • RE: Slot's restart_lsn may point to removed WAL segment after hard restart unexpectedly Hayato Kuroda (Fujitsu)
  • Re: Slot's restart_lsn may point to removed WAL segment after hard restart unexpectedly vignesh C
  • Re: Slot's restart_lsn may point to removed WAL segment after hard restart unexpectedly Alexander Korotkov
  • Re: Slot's restart_lsn may point to removed WAL segment after hard restart unexpectedly Alexander Korotkov
  • Re: Slot's restart_lsn may point to removed WAL segment after hard restart unexpectedly Amit Kapila
  • RE: Slot's restart_lsn may point to removed WAL segment after hard restart unexpectedly Hayato Kuroda (Fujitsu)
  • Re: Slot's restart_lsn may point to removed WAL segment after hard restart unexpectedly Alexander Korotkov
  • Re: Slot's restart_lsn may point to removed WAL segment after hard restart unexpectedly Alexander Korotkov
  • Re: Slot's restart_lsn may point to removed WAL segment after hard restart unexpectedly Alexander Korotkov
  • Re: Slot's restart_lsn may point to removed WAL segment after hard restart unexpectedly vignesh C
  • Re: Slot's restart_lsn may point to removed WAL segment after hard restart unexpectedly Alexander Korotkov
  • RE: Slot's restart_lsn may point to removed WAL segment after hard restart unexpectedly Zhijie Hou (Fujitsu)
  • Re: Slot's restart_lsn may point to removed WAL segment after hard restart unexpectedly Dilip Kumar
  • RE: Slot's restart_lsn may point to removed WAL segment after hard restart unexpectedly Hayato Kuroda (Fujitsu)
  • Re: Slot's restart_lsn may point to removed WAL segment after hard restart unexpectedly Dilip Kumar
  • Re: Slot's restart_lsn may point to removed WAL segment after hard restart unexpectedly Alexander Korotkov
  • RE: Slot's restart_lsn may point to removed WAL segment after hard restart unexpectedly Hayato Kuroda (Fujitsu)
  • Re: Slot's restart_lsn may point to removed WAL segment after hard restart unexpectedly Alexander Korotkov
  • RE: Slot's restart_lsn may point to removed WAL segment after hard restart unexpectedly Hayato Kuroda (Fujitsu)
  • Re: Slot's restart_lsn may point to removed WAL segment after hard restart unexpectedly Dilip Kumar
  • Re: Slot's restart_lsn may point to removed WAL segment after hard restart unexpectedly Alexander Korotkov
  • Re: Slot's restart_lsn may point to removed WAL segment after hard restart unexpectedly Amit Kapila
  • RE: Slot's restart_lsn may point to removed WAL segment after hard restart unexpectedly Hayato Kuroda (Fujitsu)
  • Re: Slot's restart_lsn may point to removed WAL segment after hard restart unexpectedly Tom Lane
  • RE: Slot's restart_lsn may point to removed WAL segment after hard restart unexpectedly Hayato Kuroda (Fujitsu)
  • Re: Slot's restart_lsn may point to removed WAL segment after hard restart unexpectedly vignesh C
  • Re: Slot's restart_lsn may point to removed WAL segment after hard restart unexpectedly Amit Kapila
  • Re: Slot's restart_lsn may point to removed WAL segment after hard restart unexpectedly Alexander Korotkov
• Fix a minor typo in jit/README Yugo Nagata
  • Re: Fix a minor typo in jit/README Daniel Gustafsson
• Re: on_error table, saving error info to a table Nishant Sharma
• Re: Fix slot synchronization with two_phase decoding enabled Nisha Moond
  • Re: Fix slot synchronization with two_phase decoding enabled Masahiko Sawada
  • Re: Fix slot synchronization with two_phase decoding enabled Nisha Moond
  • Re: Fix slot synchronization with two_phase decoding enabled Masahiko Sawada
  • Re: Fix slot synchronization with two_phase decoding enabled Nisha Moond
  • Re: Fix slot synchronization with two_phase decoding enabled Amit Kapila
  • Re: Fix slot synchronization with two_phase decoding enabled Nisha Moond
  • Re: Fix slot synchronization with two_phase decoding enabled Dilip Kumar
  • Re: Fix slot synchronization with two_phase decoding enabled Dilip Kumar
  • Re: Fix slot synchronization with two_phase decoding enabled Nisha Moond
  • Re: Fix slot synchronization with two_phase decoding enabled shveta malik
  • Re: Fix slot synchronization with two_phase decoding enabled Nisha Moond
  • Re: Fix slot synchronization with two_phase decoding enabled Ajin Cherian
  • Re: Fix slot synchronization with two_phase decoding enabled Peter Smith
  • Re: Fix slot synchronization with two_phase decoding enabled Nisha Moond
  • Re: Fix slot synchronization with two_phase decoding enabled Masahiko Sawada
  • Re: Fix slot synchronization with two_phase decoding enabled shveta malik
  • Re: Fix slot synchronization with two_phase decoding enabled Masahiko Sawada
  • Re: Fix slot synchronization with two_phase decoding enabled shveta malik
  • Re: Fix slot synchronization with two_phase decoding enabled Amit Kapila
  • Re: Fix slot synchronization with two_phase decoding enabled Dilip Kumar
  • Re: Fix slot synchronization with two_phase decoding enabled Dilip Kumar
  • Re: Fix slot synchronization with two_phase decoding enabled Masahiko Sawada
  • Re: Fix slot synchronization with two_phase decoding enabled Masahiko Sawada
  • Re: Fix slot synchronization with two_phase decoding enabled Nisha Moond
• 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 Amit Kapila
  • 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 shveta malik
  • Re: Replication slot is not able to sync up Amit Kapila
  • 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 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
  • Re: Replication slot is not able to sync up Dilip Kumar
  • RE: Replication slot is not able to sync up Zhijie Hou (Fujitsu)
• JIT works only partially with meson build? Yugo Nagata
  • Re: JIT works only partially with meson build? David Rowley
  • Re: JIT works only partially with meson build? Yugo Nagata
• Re: SQL:2011 application time Peter Eisentraut
  • Re: SQL:2011 application time Paul A Jungwirth
  • Re: SQL:2011 application time Peter Eisentraut
  • Re: SQL:2011 application time Tom Lane
• CREATE OR REPLACE FUNCTION now validates it's dependents jian he
  • Re: CREATE OR REPLACE FUNCTION now validates it's dependents Tom Lane
• 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

• Earlier messages
• Later messages