pgsql-hackers  

Messages by Thread

• • Re: POC: make mxidoff 64 bits Heikki Linnakangas
  • Re: POC: make mxidoff 64 bits Alexander Lakhin
  • Re: POC: make mxidoff 64 bits Heikki Linnakangas
  • Re: POC: make mxidoff 64 bits Heikki Linnakangas
  • Re: POC: make mxidoff 64 bits zengman
  • Re: POC: make mxidoff 64 bits Heikki Linnakangas
  • Re: POC: make mxidoff 64 bits zengman
  • Re: POC: make mxidoff 64 bits Chao Li
  • Re: POC: make mxidoff 64 bits Ashutosh Bapat
• Re: Migrate to autoconf 2.72? Aleksander Alekseev
  • Re: Migrate to autoconf 2.72? Peter Eisentraut
  • Re: Migrate to autoconf 2.72? Pavel Stehule
  • Re: Migrate to autoconf 2.72? Aleksander Alekseev
  • Re: Migrate to autoconf 2.72? Pavel Stehule
  • Re: Migrate to autoconf 2.72? Aleksander Alekseev
  • Re: Migrate to autoconf 2.72? Pavel Stehule
  • Re: Migrate to autoconf 2.72? Aleksander Alekseev
  • Re: Migrate to autoconf 2.72? Pavel Stehule
• Re: Some optimizations for COALESCE expressions during constant folding Richard Guo
  • Re: Some optimizations for COALESCE expressions during constant folding Richard Guo
  • Re: Some optimizations for COALESCE expressions during constant folding Matheus Alcantara
  • Re: Some optimizations for COALESCE expressions during constant folding Richard Guo
  • Re: Some optimizations for COALESCE expressions during constant folding Matheus Alcantara
  • Re: Some optimizations for COALESCE expressions during constant folding Richard Guo
• missing PG_IO_ALIGN_SIZE uses Peter Eisentraut
  • Re: missing PG_IO_ALIGN_SIZE uses Chao Li
  • Re: missing PG_IO_ALIGN_SIZE uses Peter Eisentraut
  • Re: missing PG_IO_ALIGN_SIZE uses Thomas Munro
• Re: Move WAL/RMGR sequence code into its own file and header Michael Paquier
• Re: Consistently use the XLogRecPtrIsInvalid() macro Bertrand Drouvot
  • Re: Consistently use the XLogRecPtrIsInvalid() macro Peter Eisentraut
  • Re: Consistently use the XLogRecPtrIsInvalid() macro Bertrand Drouvot
• Re: alignas (C11) Peter Eisentraut
• Re: Refactoring: Use soft error reporting for *_opt_overflow functions of date/timestamp Michael Paquier
  • Re: Refactoring: Use soft error reporting for *_opt_overflow functions of date/timestamp Amul Sul
  • Re: Refactoring: Use soft error reporting for *_opt_overflow functions of date/timestamp Michael Paquier
  • Re: Refactoring: Use soft error reporting for *_opt_overflow functions of date/timestamp Amit Langote
• Re: Row pattern recognition Tatsuo Ishii
  • Re: Row pattern recognition Tatsuo Ishii
  • Re: Row pattern recognition Henson Choi
  • Re: Row pattern recognition Tatsuo Ishii
  • Re: Row pattern recognition Tatsuo Ishii
  • Re: Row pattern recognition Henson Choi
  • Re: Row pattern recognition Tatsuo Ishii
  • Re: Row pattern recognition Henson Choi
  • Re: Row pattern recognition Tatsuo Ishii
  • Re: Row pattern recognition Jacob Champion
  • Re: Row pattern recognition Tatsuo Ishii
  • Re: Row pattern recognition Jacob Champion
• Re: Remove unused function parameters, part 2: replication Bertrand Drouvot
  • Re: Remove unused function parameters, part 2: replication Michael Paquier
  • Re: Remove unused function parameters, part 2: replication Daniel Gustafsson
  • Re: Remove unused function parameters, part 2: replication Bertrand Drouvot
  • Re: Remove unused function parameters, part 2: replication Daniel Gustafsson
  • Re: Remove unused function parameters, part 2: replication Bertrand Drouvot
  • Re: Remove unused function parameters, part 2: replication Bertrand Drouvot
• UPDATE run check constraints for affected columns only jian he
  • Re: UPDATE run check constraints for affected columns only Tom Lane
  • 回复: UPDATE run check constraints for affected columns only li carol
  • Re: UPDATE run check constraints for affected columns only jian he
• Re: Simplify code building the LR conflict messages Amit Kapila
  • Re: Simplify code building the LR conflict messages Álvaro Herrera
  • Re: Simplify code building the LR conflict messages Mihail Nikalayeu
  • Re: Simplify code building the LR conflict messages Amit Kapila
  • Re: Simplify code building the LR conflict messages Amit Kapila
  • Re: Simplify code building the LR conflict messages Masahiko Sawada
• Re: Eliminating SPI / SQL from some RI triggers - take 3 Junwang Zhao
• Re: POC: enable logical decoding when wal_level = 'replica' without a server restart Masahiko Sawada
  • Re: POC: enable logical decoding when wal_level = 'replica' without a server restart Peter Smith
  • Re: POC: enable logical decoding when wal_level = 'replica' without a server restart Masahiko Sawada
  • Re: POC: enable logical decoding when wal_level = 'replica' without a server restart Masahiko Sawada
  • Re: POC: enable logical decoding when wal_level = 'replica' without a server restart shveta malik
  • Re: POC: enable logical decoding when wal_level = 'replica' without a server restart Masahiko Sawada
  • Re: POC: enable logical decoding when wal_level = 'replica' without a server restart shveta malik
  • Re: POC: enable logical decoding when wal_level = 'replica' without a server restart Masahiko Sawada
  • Re: POC: enable logical decoding when wal_level = 'replica' without a server restart shveta malik
  • Re: POC: enable logical decoding when wal_level = 'replica' without a server restart shveta malik
  • Re: POC: enable logical decoding when wal_level = 'replica' without a server restart shveta malik
  • Re: POC: enable logical decoding when wal_level = 'replica' without a server restart Masahiko Sawada
  • Re: POC: enable logical decoding when wal_level = 'replica' without a server restart Masahiko Sawada
  • Re: POC: enable logical decoding when wal_level = 'replica' without a server restart Masahiko Sawada
  • Re: POC: enable logical decoding when wal_level = 'replica' without a server restart Amit Kapila
  • Re: POC: enable logical decoding when wal_level = 'replica' without a server restart Masahiko Sawada
  • Re: POC: enable logical decoding when wal_level = 'replica' without a server restart Amit Kapila
  • Re: POC: enable logical decoding when wal_level = 'replica' without a server restart Amit Kapila
  • Re: POC: enable logical decoding when wal_level = 'replica' without a server restart shveta malik
  • Re: POC: enable logical decoding when wal_level = 'replica' without a server restart shveta malik
  • Re: POC: enable logical decoding when wal_level = 'replica' without a server restart Masahiko Sawada
  • Re: POC: enable logical decoding when wal_level = 'replica' without a server restart Amit Kapila
  • Re: POC: enable logical decoding when wal_level = 'replica' without a server restart shveta malik
  • Re: POC: enable logical decoding when wal_level = 'replica' without a server restart Masahiko Sawada
  • Re: POC: enable logical decoding when wal_level = 'replica' without a server restart Peter Smith
  • Re: POC: enable logical decoding when wal_level = 'replica' without a server restart Masahiko Sawada
  • Re: POC: enable logical decoding when wal_level = 'replica' without a server restart shveta malik
  • Re: POC: enable logical decoding when wal_level = 'replica' without a server restart Masahiko Sawada
  • RE: POC: enable logical decoding when wal_level = 'replica' without a server restart Zhijie Hou (Fujitsu)
  • Re: POC: enable logical decoding when wal_level = 'replica' without a server restart Masahiko Sawada
  • Re: POC: enable logical decoding when wal_level = 'replica' without a server restart Peter Smith
  • Re: POC: enable logical decoding when wal_level = 'replica' without a server restart Masahiko Sawada
  • Re: POC: enable logical decoding when wal_level = 'replica' without a server restart shveta malik
  • Re: POC: enable logical decoding when wal_level = 'replica' without a server restart Masahiko Sawada
  • Re: POC: enable logical decoding when wal_level = 'replica' without a server restart shveta malik
  • Re: POC: enable logical decoding when wal_level = 'replica' without a server restart shveta malik
  • Re: POC: enable logical decoding when wal_level = 'replica' without a server restart Masahiko Sawada
  • Re: POC: enable logical decoding when wal_level = 'replica' without a server restart vignesh C
  • Re: POC: enable logical decoding when wal_level = 'replica' without a server restart Masahiko Sawada
  • Re: POC: enable logical decoding when wal_level = 'replica' without a server restart Masahiko Sawada
• Re: CAST(... ON DEFAULT) - WIP build on top of Error-Safe User Functions Corey Huinker
  • Re: CAST(... ON DEFAULT) - WIP build on top of Error-Safe User Functions jian he
  • Re: CAST(... ON DEFAULT) - WIP build on top of Error-Safe User Functions Kirill Reshke
  • Re: CAST(... ON DEFAULT) - WIP build on top of Error-Safe User Functions Corey Huinker
  • Re: CAST(... ON DEFAULT) - WIP build on top of Error-Safe User Functions Amul Sul
  • Re: CAST(... ON DEFAULT) - WIP build on top of Error-Safe User Functions Amul Sul
  • Re: CAST(... ON DEFAULT) - WIP build on top of Error-Safe User Functions Amul Sul
• Re: [PATCH] Expose checkpoint timestamp and duration in pg_stat_checkpointer Soumya S Murali
  • Re: [PATCH] Expose checkpoint timestamp and duration in pg_stat_checkpointer Michael Banck
  • Re: [PATCH] Expose checkpoint timestamp and duration in pg_stat_checkpointer Soumya S Murali
• Re: Add GoAway protocol message for graceful but fast server shutdown/switchover Ajit Awekar
• Re: Parallel Apply Dilip Kumar
  • RE: Parallel Apply Hayato Kuroda (Fujitsu)
  • Re: Parallel Apply Dilip Kumar
  • RE: Parallel Apply Hayato Kuroda (Fujitsu)
  • Re: Parallel Apply Andrei Lepikhov
  • RE: Parallel Apply Hayato Kuroda (Fujitsu)
  • Re: Parallel Apply Andrei Lepikhov
  • Re: Parallel Apply Amit Kapila
  • RE: Parallel Apply Hayato Kuroda (Fujitsu)
• Re: Proposal: Conflict log history table for Logical Replication Dilip Kumar
  • Re: Proposal: Conflict log history table for Logical Replication Amit Kapila
  • Re: Proposal: Conflict log history table for Logical Replication Dilip Kumar
  • Re: Proposal: Conflict log history table for Logical Replication Dilip Kumar
  • Re: Proposal: Conflict log history table for Logical Replication Amit Kapila
  • Re: Proposal: Conflict log history table for Logical Replication Dilip Kumar
  • Re: Proposal: Conflict log history table for Logical Replication Dilip Kumar
  • Re: Proposal: Conflict log history table for Logical Replication shveta malik
  • Re: Proposal: Conflict log history table for Logical Replication Masahiko Sawada
  • Re: Proposal: Conflict log history table for Logical Replication Dilip Kumar
  • Re: Proposal: Conflict log history table for Logical Replication Amit Kapila
  • Re: Proposal: Conflict log history table for Logical Replication Amit Kapila
  • Re: Proposal: Conflict log history table for Logical Replication shveta malik
  • Re: Proposal: Conflict log history table for Logical Replication Dilip Kumar
  • Re: Proposal: Conflict log history table for Logical Replication Dilip Kumar
  • Re: Proposal: Conflict log history table for Logical Replication Amit Kapila
  • Re: Proposal: Conflict log history table for Logical Replication Dilip Kumar
  • Re: Proposal: Conflict log history table for Logical Replication Amit Kapila
  • Re: Proposal: Conflict log history table for Logical Replication Dilip Kumar
  • Re: Proposal: Conflict log history table for Logical Replication Amit Kapila
  • Re: Proposal: Conflict log history table for Logical Replication Dilip Kumar
  • Re: Proposal: Conflict log history table for Logical Replication shveta malik
  • Re: Proposal: Conflict log history table for Logical Replication Dilip Kumar
  • Re: Proposal: Conflict log history table for Logical Replication Amit Kapila
  • Re: Proposal: Conflict log history table for Logical Replication shveta malik
  • Re: Proposal: Conflict log history table for Logical Replication Dilip Kumar
  • Re: Proposal: Conflict log history table for Logical Replication shveta malik
  • Re: Proposal: Conflict log history table for Logical Replication Dilip Kumar
  • Re: Proposal: Conflict log history table for Logical Replication vignesh C
  • Re: Proposal: Conflict log history table for Logical Replication Amit Kapila
  • Re: Proposal: Conflict log history table for Logical Replication shveta malik
  • Re: Proposal: Conflict log history table for Logical Replication Dilip Kumar
  • Re: Proposal: Conflict log history table for Logical Replication shveta malik
  • Re: Proposal: Conflict log history table for Logical Replication Dilip Kumar
  • Re: Proposal: Conflict log history table for Logical Replication Dilip Kumar
  • Re: Proposal: Conflict log history table for Logical Replication Amit Kapila
  • Re: Proposal: Conflict log history table for Logical Replication Dilip Kumar
  • Re: Proposal: Conflict log history table for Logical Replication Dilip Kumar
  • Re: Proposal: Conflict log history table for Logical Replication Amit Kapila
  • Re: Proposal: Conflict log history table for Logical Replication Masahiko Sawada
  • Re: Proposal: Conflict log history table for Logical Replication Amit Kapila
  • Re: Proposal: Conflict log history table for Logical Replication Dilip Kumar
  • Re: Proposal: Conflict log history table for Logical Replication shveta malik
  • Re: Proposal: Conflict log history table for Logical Replication Amit Kapila
  • Re: Proposal: Conflict log history table for Logical Replication Dilip Kumar
  • Re: Proposal: Conflict log history table for Logical Replication Masahiko Sawada
  • Re: Proposal: Conflict log history table for Logical Replication shveta malik
  • Re: Proposal: Conflict log history table for Logical Replication Peter Smith
  • Re: Proposal: Conflict log history table for Logical Replication Dilip Kumar
  • Re: Proposal: Conflict log history table for Logical Replication Peter Smith
  • Re: Proposal: Conflict log history table for Logical Replication Dilip Kumar
  • Re: Proposal: Conflict log history table for Logical Replication Amit Kapila
  • Re: Proposal: Conflict log history table for Logical Replication Peter Smith
  • Re: Proposal: Conflict log history table for Logical Replication Amit Kapila
  • Re: Proposal: Conflict log history table for Logical Replication Dilip Kumar
  • Re: Proposal: Conflict log history table for Logical Replication Amit Kapila
  • Re: Proposal: Conflict log history table for Logical Replication Dilip Kumar
  • Re: Proposal: Conflict log history table for Logical Replication Amit Kapila
  • Re: Proposal: Conflict log history table for Logical Replication shveta malik
  • Re: Proposal: Conflict log history table for Logical Replication Dilip Kumar
  • Re: Proposal: Conflict log history table for Logical Replication shveta malik
  • Re: Proposal: Conflict log history table for Logical Replication Dilip Kumar
  • Re: Proposal: Conflict log history table for Logical Replication shveta malik
  • Re: Proposal: Conflict log history table for Logical Replication Peter Smith
  • Re: Proposal: Conflict log history table for Logical Replication vignesh C
  • Re: Proposal: Conflict log history table for Logical Replication vignesh C
  • Re: Proposal: Conflict log history table for Logical Replication shveta malik
  • Re: Proposal: Conflict log history table for Logical Replication Dilip Kumar
  • Re: Proposal: Conflict log history table for Logical Replication shveta malik
  • Re: Proposal: Conflict log history table for Logical Replication Dilip Kumar
  • Re: Proposal: Conflict log history table for Logical Replication Amit Kapila
  • Re: Proposal: Conflict log history table for Logical Replication Dilip Kumar
  • Re: Proposal: Conflict log history table for Logical Replication shveta malik

• Earlier messages
• Later messages