pgsql-hackers  

Messages by Thread

• • Re: [WIP]Vertical Clustered Index (columnar store extension) - take2 Peter Smith
  • Re: [WIP]Vertical Clustered Index (columnar store extension) - take2 Peter Smith
  • Re: [WIP]Vertical Clustered Index (columnar store extension) - take2 Timur Magomedov
  • Re: [WIP]Vertical Clustered Index (columnar store extension) - take2 Peter Smith
  • Re: [WIP]Vertical Clustered Index (columnar store extension) - take2 Peter Smith
  • Re: [WIP]Vertical Clustered Index (columnar store extension) - take2 Timur Magomedov
  • Re: [WIP]Vertical Clustered Index (columnar store extension) - take2 Peter Smith
  • Re: [WIP]Vertical Clustered Index (columnar store extension) - take2 Timur Magomedov
  • Re: [WIP]Vertical Clustered Index (columnar store extension) - take2 Timur Magomedov
  • Re: [WIP]Vertical Clustered Index (columnar store extension) - take2 Peter Smith
  • Re: [WIP]Vertical Clustered Index (columnar store extension) - take2 Peter Smith
  • Re: [WIP]Vertical Clustered Index (columnar store extension) - take2 Jim Nasby
  • Re: [WIP]Vertical Clustered Index (columnar store extension) - take2 Tomas Vondra
  • Re: [WIP]Vertical Clustered Index (columnar store extension) - take2 Jim Nasby
  • Re: [WIP]Vertical Clustered Index (columnar store extension) - take2 Jim Nasby
  • Re: [WIP]Vertical Clustered Index (columnar store extension) - take2 Peter Smith
  • RE: [WIP]Vertical Clustered Index (columnar store extension) - take2 Aya Iwata (Fujitsu)
  • Re: [WIP]Vertical Clustered Index (columnar store extension) - take2 Peter Smith
  • Re: [WIP]Vertical Clustered Index (columnar store extension) - take2 Japin Li
• 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
• 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 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: Assert("vacrel->eager_scan_remaining_successes > 0") Masahiko Sawada
  • Re: Assert("vacrel->eager_scan_remaining_successes > 0") Melanie Plageman
  • Re: Assert("vacrel->eager_scan_remaining_successes > 0") Masahiko Sawada
• 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
• 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
  • Re: mention unused_oids script in pg_proc.dat Peter Eisentraut
• 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
• Re: Addition of %b/backend_type in log_line_prefix of TAP test logs Fujii Masao
  • Re: Addition of %b/backend_type in log_line_prefix of TAP test logs Michael Paquier
  • Re: Addition of %b/backend_type in log_line_prefix of TAP test logs Michael Paquier
  • Re: Addition of %b/backend_type in log_line_prefix of TAP test logs Michael Paquier
  • Re: Addition of %b/backend_type in log_line_prefix of TAP test logs Andres Freund
• Re: Prevent an error on attaching/creating a DSM/DSA from an interrupt handler. Daniel Gustafsson
• Re: [Util] Warn and Remove Invalid GUCs Shaik Mohammad Mujeeb
  • Re: [Util] Warn and Remove Invalid GUCs Shaik Mohammad Mujeeb
• 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 Florents Tselai
  • Re: PATCH: jsonpath string methods: lower, upper, initcap, l/r/btrim, replace, split_part Tom Lane
  • 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 David E. Wheeler
  • 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 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 David E. Wheeler
  • 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 David E. Wheeler
  • Re: PATCH: jsonpath string methods: lower, upper, initcap, l/r/btrim, replace, split_part David E. Wheeler
• Disallow concurrent ALTER DOMAIN and DROP DOMAIN jian he
• Re: Relstats after VACUUM FULL and CLUSTER Erik Nordström
  • Re: Relstats after VACUUM FULL and CLUSTER Sami Imseih
• Re: Update LDAP Protocol in fe-connect.c to v3 Peter Eisentraut
• Re: Minor adjustment to pg_aios output naming Atsushi Torikoshi
• Re: RFC: Logging plan of the running query Atsushi Torikoshi
  • Re: RFC: Logging plan of the running query torikoshia
• 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: 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: Enable data checksums by default Heikki Linnakangas
  • Re: Enable data checksums by default Peter Eisentraut
  • Re: Enable data checksums by default Tomas Vondra
  • Re: Enable data checksums by default Peter Eisentraut
  • Re: Enable data checksums by default Daniel Gustafsson
  • Re: Enable data checksums by default Tomas Vondra
  • Re: Enable data checksums by default Daniel Gustafsson
  • Re: Enable data checksums by default Bruce Momjian
  • Re: Enable data checksums by default Christoph Berg
  • Re: Enable data checksums by default Peter Eisentraut
  • Re: Enable data checksums by default Bruce Momjian
• RE: Re: Re: psql : \dn+ to show default schema privileges 노명석
• Re: XMLSerialize: version and explicit XML declaration Jim Jones
• Re: Conflict detection for update_deleted in logical replication shveta malik
  • Re: Conflict detection for update_deleted in logical replication Amit Kapila
  • RE: Conflict detection for update_deleted in logical replication Zhijie Hou (Fujitsu)
  • Re: Conflict detection for update_deleted in logical replication Amit Kapila
  • Re: Conflict detection for update_deleted in logical replication shveta malik
  • Re: Conflict detection for update_deleted in logical replication Amit Kapila
  • Re: Conflict detection for update_deleted in logical replication shveta malik
  • Re: Conflict detection for update_deleted in logical replication Amit Kapila
  • Re: Conflict detection for update_deleted in logical replication shveta malik
  • RE: Conflict detection for update_deleted in logical replication Zhijie Hou (Fujitsu)
  • Re: Conflict detection for update_deleted in logical replication shveta malik
  • Re: Conflict detection for update_deleted in logical replication Amit Kapila
  • Re: Conflict detection for update_deleted in logical replication shveta malik
  • Re: Conflict detection for update_deleted in logical replication shveta malik
  • Re: Conflict detection for update_deleted in logical replication shveta malik
  • Re: Conflict detection for update_deleted in logical replication shveta malik
  • Re: Conflict detection for update_deleted in logical replication Amit Kapila
  • Re: Conflict detection for update_deleted in logical replication Amit Kapila
  • Re: Conflict detection for update_deleted in logical replication shveta malik
  • Re: Conflict detection for update_deleted in logical replication shveta malik
  • Re: Conflict detection for update_deleted in logical replication shveta malik
  • Re: Conflict detection for update_deleted in logical replication Amit Kapila
  • Re: Conflict detection for update_deleted in logical replication shveta malik
  • Re: Conflict detection for update_deleted in logical replication shveta malik
  • RE: Conflict detection for update_deleted in logical replication Zhijie Hou (Fujitsu)
  • Re: Conflict detection for update_deleted in logical replication shveta malik
  • Re: Conflict detection for update_deleted in logical replication shveta malik
  • Re: Conflict detection for update_deleted in logical replication Amit Kapila
  • Re: Conflict detection for update_deleted in logical replication Dilip Kumar
  • Re: Conflict detection for update_deleted in logical replication Dilip Kumar
  • Re: Conflict detection for update_deleted in logical replication Amit Kapila
  • Re: Conflict detection for update_deleted in logical replication Dilip Kumar
  • Re: Conflict detection for update_deleted in logical replication Dilip Kumar
  • RE: Conflict detection for update_deleted in logical replication Zhijie Hou (Fujitsu)
  • Re: Conflict detection for update_deleted in logical replication Dilip Kumar
  • Re: Conflict detection for update_deleted in logical replication Amit Kapila
  • Re: Conflict detection for update_deleted in logical replication Dilip Kumar

• Earlier messages
• Later messages