pgsql-hackers  

Messages by Thread

• • Re: Proposal: Conflict log history table for Logical Replication Peter Smith
  • Re: Proposal: Conflict log history table for Logical Replication Peter Smith
  • Re: Proposal: Conflict log history table for Logical Replication Shlok Kyal
  • 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 Peter Smith
  • Re: Proposal: Conflict log history table for Logical Replication Peter Smith
  • Re: Proposal: Conflict log history table for Logical Replication Peter Smith
  • Re: Proposal: Conflict log history table for Logical Replication Peter Smith
  • Re: Proposal: Conflict log history table for Logical Replication shveta malik
  • 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 shveta malik
  • Re: Proposal: Conflict log history table for Logical Replication Shlok Kyal
  • Re: Proposal: Conflict log history table for Logical Replication shveta malik
  • Re: Proposal: Conflict log history table for Logical Replication Nisha Moond
  • Re: Proposal: Conflict log history table for Logical Replication Nisha Moond
  • 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 shveta malik
  • 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 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 vignesh C
  • 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 Amit Kapila
  • 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 vignesh C
  • 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 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 Nisha Moond
  • 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 Peter Smith
  • Re: Proposal: Conflict log history table for Logical Replication Nisha Moond
  • Re: Proposal: Conflict log history table for Logical Replication Nisha Moond
  • Re: Proposal: Conflict log history table for Logical Replication Zsolt Parragi
  • Re: Proposal: Conflict log history table for Logical Replication Peter Smith
  • Re: Proposal: Conflict log history table for Logical Replication Nisha Moond
  • 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 Peter Smith
  • Re: Proposal: Conflict log history table for Logical Replication Peter Smith
  • Re: Proposal: Conflict log history table for Logical Replication shveta malik
  • 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 Peter Smith
  • Re: Proposal: Conflict log history table for Logical Replication vignesh C
  • Re: Proposal: Conflict log history table for Logical Replication Dilip Kumar
  • Re: Proposal: Conflict log history table for Logical Replication Dilip Kumar
• Re: Parallel Apply Amit Kapila
  • Re: Parallel Apply shveta malik
  • Re: Parallel Apply shveta malik
  • RE: Parallel Apply Hayato Kuroda (Fujitsu)
  • Re: Parallel Apply Peter Smith
  • Re: Parallel Apply Peter Smith
  • Re: Parallel Apply shveta malik
  • RE: Parallel Apply Zhijie Hou (Fujitsu)
  • Re: Parallel Apply shveta malik
  • RE: Parallel Apply Zhijie Hou (Fujitsu)
  • Re: Parallel Apply shveta malik
  • Re: Parallel Apply Amit Kapila
  • RE: Parallel Apply Hayato Kuroda (Fujitsu)
  • Re: Parallel Apply Peter Smith
  • RE: Parallel Apply Zhijie Hou (Fujitsu)
  • Re: Parallel Apply shveta malik
  • Re: Parallel Apply shveta malik
  • Re: Parallel Apply shveta malik
  • Re: Parallel Apply shveta malik
  • Re: Parallel Apply shveta malik
  • RE: Parallel Apply Zhijie Hou (Fujitsu)
  • RE: Parallel Apply Zhijie Hou (Fujitsu)
  • Re: Parallel Apply Dilip Kumar
  • RE: Parallel Apply Zhijie Hou (Fujitsu)
  • Re: Parallel Apply shveta malik
  • RE: Parallel Apply Hayato Kuroda (Fujitsu)
  • RE: Parallel Apply Hayato Kuroda (Fujitsu)
• [PATCH] Extend MXactCache lifetime from per-transaction to per-session JoongHyuk Shin
• Fix pg_upgrade to detect invalid logical replication slots on PG19 Lakshmi N
  • Re: Fix pg_upgrade to detect invalid logical replication slots on PG19 shveta malik
  • Re: Fix pg_upgrade to detect invalid logical replication slots on PG19 Masahiko Sawada
  • Re: Fix pg_upgrade to detect invalid logical replication slots on PG19 Masahiko Sawada
  • Re: Fix pg_upgrade to detect invalid logical replication slots on PG19 Chao Li
• Re: Fix stats reporting delays in logical parallel apply worker Amit Kapila
• Re: ECPG: inconsistent behavior with the document in “GET/SET DESCRIPTOR.” lakshmi
  • RE: ECPG: inconsistent behavior with the document in “GET/SET DESCRIPTOR.” Hayato Kuroda (Fujitsu)
  • Re: ECPG: inconsistent behavior with the document in “GET/SET DESCRIPTOR.” lakshmi
  • Re: ECPG: inconsistent behavior with the document in “GET/SET DESCRIPTOR.” lakshmi
  • RE: ECPG: inconsistent behavior with the document in “GET/SET DESCRIPTOR.” Masashi Kamura (Fujitsu)
  • RE: ECPG: inconsistent behavior with the document in “GET/SET DESCRIPTOR.” Hayato Kuroda (Fujitsu)
  • Re: ECPG: inconsistent behavior with the document in “GET/SET DESCRIPTOR.” lakshmi
  • RE: ECPG: inconsistent behavior with the document in “GET/SET DESCRIPTOR.” Hayato Kuroda (Fujitsu)
  • Re: ECPG: inconsistent behavior with the document in “GET/SET DESCRIPTOR.” Fujii Masao
  • RE: ECPG: inconsistent behavior with the document in “GET/SET DESCRIPTOR.” Hayato Kuroda (Fujitsu)
  • Re: ECPG: inconsistent behavior with the document in “GET/SET DESCRIPTOR.” Fujii Masao
  • RE: ECPG: inconsistent behavior with the document in “GET/SET DESCRIPTOR.” Masashi Kamura (Fujitsu)
• [PATCH] Reject ENCODING option for COPY TO FORMAT JSON Ayush Tiwari
  • Re: [PATCH] Reject ENCODING option for COPY TO FORMAT JSON Daniel Gustafsson
  • Re: [PATCH] Reject ENCODING option for COPY TO FORMAT JSON Ayush Tiwari
  • Re: [PATCH] Reject ENCODING option for COPY TO FORMAT JSON Tom Lane
  • Re: [PATCH] Reject ENCODING option for COPY TO FORMAT JSON Ayush Tiwari
  • Re: [PATCH] Reject ENCODING option for COPY TO FORMAT JSON Ayush Tiwari
  • Re: [PATCH] Reject ENCODING option for COPY TO FORMAT JSON Ayush Tiwari
  • Re: [PATCH] Reject ENCODING option for COPY TO FORMAT JSON Andrew Dunstan
  • Re: [PATCH] Reject ENCODING option for COPY TO FORMAT JSON Ayush Tiwari
  • Re: [PATCH] Reject ENCODING option for COPY TO FORMAT JSON Andrew Dunstan
• Re: Bug: Rule actions see wrong values for generated columns (NEW.gen reads OLD value) Richard Guo
  • Re: Bug: Rule actions see wrong values for generated columns (NEW.gen reads OLD value) Richard Guo
  • Re: Bug: Rule actions see wrong values for generated columns (NEW.gen reads OLD value) Dean Rasheed
  • Re: Bug: Rule actions see wrong values for generated columns (NEW.gen reads OLD value) Richard Guo
• Cleanup: Replace sscanf with strtol/strtoul in snapmgr Amul Sul
  • Re: Cleanup: Replace sscanf with strtol/strtoul in snapmgr Andreas Karlsson
  • Re: Cleanup: Replace sscanf with strtol/strtoul in snapmgr Tristan Partin
  • Re: Cleanup: Replace sscanf with strtol/strtoul in snapmgr Amul Sul
  • Re: Cleanup: Replace sscanf with strtol/strtoul in snapmgr Tristan Partin
• Re: POC: Comparison of partitioning key values Amit Langote
• Re: EXCEPT TABLE - Case inconsistency for describe \d and \dRp+ Peter Smith
  • Re: EXCEPT TABLE - Case inconsistency for describe \d and \dRp+ vignesh C
  • Re: EXCEPT TABLE - Case inconsistency for describe \d and \dRp+ Peter Smith
  • Re: EXCEPT TABLE - Case inconsistency for describe \d and \dRp+ Yuchen Li
  • Re: EXCEPT TABLE - Case inconsistency for describe \d and \dRp+ Peter Smith
  • Re: EXCEPT TABLE - Case inconsistency for describe \d and \dRp+ Amit Kapila
  • Re: EXCEPT TABLE - Case inconsistency for describe \d and \dRp+ Peter Smith
  • Re: EXCEPT TABLE - Case inconsistency for describe \d and \dRp+ Amit Kapila
  • Re: EXCEPT TABLE - Case inconsistency for describe \d and \dRp+ Álvaro Herrera
• Re: DOCS - CREATE PUBLICATION ... EXCEPT missing details on ONLY Peter Smith
  • Re: DOCS - CREATE PUBLICATION ... EXCEPT missing details on ONLY Amit Kapila
  • Re: DOCS - CREATE PUBLICATION ... EXCEPT missing details on ONLY Peter Smith
• Re: MERGE PARTITIONS and DEPENDS ON EXTENSION. Dmitry Koval
  • Re: MERGE PARTITIONS and DEPENDS ON EXTENSION. Matheus Alcantara
  • Re: MERGE PARTITIONS and DEPENDS ON EXTENSION. Alexander Korotkov
  • Re: MERGE PARTITIONS and DEPENDS ON EXTENSION. Matheus Alcantara
  • Re: MERGE PARTITIONS and DEPENDS ON EXTENSION. Alexander Korotkov
  • Re: MERGE PARTITIONS and DEPENDS ON EXTENSION. Matheus Alcantara
  • Re: MERGE PARTITIONS and DEPENDS ON EXTENSION. Alexander Korotkov
  • Re: MERGE PARTITIONS and DEPENDS ON EXTENSION. Kirill Reshke
  • Re: MERGE PARTITIONS and DEPENDS ON EXTENSION. Matheus Alcantara
  • Re: MERGE PARTITIONS and DEPENDS ON EXTENSION. Kirill Reshke
  • Re: MERGE PARTITIONS and DEPENDS ON EXTENSION. Matheus Alcantara
  • Re: MERGE PARTITIONS and DEPENDS ON EXTENSION. Alexander Korotkov
  • Re: MERGE PARTITIONS and DEPENDS ON EXTENSION. Kirill Reshke
  • Re: MERGE PARTITIONS and DEPENDS ON EXTENSION. Matheus Alcantara
  • Re: MERGE PARTITIONS and DEPENDS ON EXTENSION. Alexander Korotkov
  • Re: MERGE PARTITIONS and DEPENDS ON EXTENSION. Matheus Alcantara
  • Re: MERGE PARTITIONS and DEPENDS ON EXTENSION. Matheus Alcantara
• Re: some extra warnings from MSVC Michael Paquier
• collecting photos related to Postgres history & community for pgconf.dev Tomas Vondra
• Re: FOR PORTION OF does not recompute GENERATED STORED columns that depend on the range column Paul A Jungwirth
  • Re: FOR PORTION OF does not recompute GENERATED STORED columns that depend on the range column jian he
  • Re: FOR PORTION OF does not recompute GENERATED STORED columns that depend on the range column Paul A Jungwirth
  • Re: FOR PORTION OF does not recompute GENERATED STORED columns that depend on the range column jian he
  • Re: FOR PORTION OF does not recompute GENERATED STORED columns that depend on the range column Paul A Jungwirth
  • Re: FOR PORTION OF does not recompute GENERATED STORED columns that depend on the range column Paul A Jungwirth
  • Re: FOR PORTION OF does not recompute GENERATED STORED columns that depend on the range column Peter Eisentraut
  • Re: FOR PORTION OF does not recompute GENERATED STORED columns that depend on the range column Paul A Jungwirth
  • Re: FOR PORTION OF does not recompute GENERATED STORED columns that depend on the range column jian he
  • Re: FOR PORTION OF does not recompute GENERATED STORED columns that depend on the range column Chao Li
  • Re: FOR PORTION OF does not recompute GENERATED STORED columns that depend on the range column Chao Li
  • Re: FOR PORTION OF does not recompute GENERATED STORED columns that depend on the range column Chao Li
  • Re: FOR PORTION OF does not recompute GENERATED STORED columns that depend on the range column Paul A Jungwirth
  • Re: FOR PORTION OF does not recompute GENERATED STORED columns that depend on the range column Chao Li
  • Re: FOR PORTION OF does not recompute GENERATED STORED columns that depend on the range column Paul A Jungwirth
  • Re: FOR PORTION OF does not recompute GENERATED STORED columns that depend on the range column Chao Li
  • Re: FOR PORTION OF does not recompute GENERATED STORED columns that depend on the range column jian he
  • Re: FOR PORTION OF does not recompute GENERATED STORED columns that depend on the range column Paul A Jungwirth
  • Re: FOR PORTION OF does not recompute GENERATED STORED columns that depend on the range column Nathan Bossart
  • Re: FOR PORTION OF does not recompute GENERATED STORED columns that depend on the range column Paul A Jungwirth
  • Re: FOR PORTION OF does not recompute GENERATED STORED columns that depend on the range column Paul A Jungwirth
  • Re: FOR PORTION OF does not recompute GENERATED STORED columns that depend on the range column Paul A Jungwirth
  • Re: FOR PORTION OF does not recompute GENERATED STORED columns that depend on the range column jian he
  • Re: FOR PORTION OF does not recompute GENERATED STORED columns that depend on the range column Paul A Jungwirth
• [BUG] Race in online checksums launcher_exit() Ayush Tiwari
  • Re: [BUG] Race in online checksums launcher_exit() Daniel Gustafsson
  • Re: [BUG] Race in online checksums launcher_exit() Ayush Tiwari
• Re: Typos in the code and README Alexander Lakhin
  • Re: Typos in the code and README Alexander Lakhin
  • Re: Typos in the code and README Michael Paquier
  • Re: Typos in the code and README Daniil Davydov
• Possible premature SNAPBUILD_CONSISTENT with DB-specific running_xacts SATYANARAYANA NARLAPURAM
  • Re: Possible premature SNAPBUILD_CONSISTENT with DB-specific running_xacts Amit Kapila
• Re: DELETE/UPDATE FOR PORTION OF with rule system is not working Paul A Jungwirth
  • Re: DELETE/UPDATE FOR PORTION OF with rule system is not working Peter Eisentraut
• Re: [PATCH] Fix hashed ScalarArrayOp semantics for NULL LHS with non-strict comparators David Rowley
  • Re: [PATCH] Fix hashed ScalarArrayOp semantics for NULL LHS with non-strict comparators David Rowley
  • Re: [PATCH] Fix hashed ScalarArrayOp semantics for NULL LHS with non-strict comparators Tom Lane
  • Re: [PATCH] Fix hashed ScalarArrayOp semantics for NULL LHS with non-strict comparators Chengpeng Yan
  • Re: [PATCH] Fix hashed ScalarArrayOp semantics for NULL LHS with non-strict comparators David Rowley
  • Re: [PATCH] Fix hashed ScalarArrayOp semantics for NULL LHS with non-strict comparators Chengpeng Yan

• Earlier messages
• Later messages