pgsql-hackers  

Messages by Thread

• • Re: fix prev link in docs Nathan Bossart
• Re: [PATCH] Improving index selection for logical replication apply with replica identity full Bharath Rupireddy
  • RE: [PATCH] Improving index selection for logical replication apply with replica identity full Hayato Kuroda (Fujitsu)
  • Re: [PATCH] Improving index selection for logical replication apply with replica identity full Önder Kalacı
  • RE: [PATCH] Improving index selection for logical replication apply with replica identity full Hayato Kuroda (Fujitsu)
  • Re: [PATCH] Improving index selection for logical replication apply with replica identity full Bharath Rupireddy
  • Re: [PATCH] Improving index selection for logical replication apply with replica identity full Ethan Mertz
  • Re: [PATCH] Improving index selection for logical replication apply with replica identity full Bharath Rupireddy
  • Re: [PATCH] Improving index selection for logical replication apply with replica identity full Ethan Mertz
• Re: [PATCH] Doc: document standard_conforming_strings dump/restore incompatibility Nathan Bossart
  • Re: [PATCH] Doc: document standard_conforming_strings dump/restore incompatibility Tom Lane
  • Re: [PATCH] Doc: document standard_conforming_strings dump/restore incompatibility Tom Lane
  • Re: [PATCH] Doc: document standard_conforming_strings dump/restore incompatibility Baji Shaik
  • Re: [PATCH] Doc: document standard_conforming_strings dump/restore incompatibility Bruce Momjian
  • Re: [PATCH] Doc: document standard_conforming_strings dump/restore incompatibility Tom Lane
  • Re: [PATCH] Doc: document standard_conforming_strings dump/restore incompatibility Bruce Momjian
• Re: PG19beta1: GCC 16.1.1 warning: ‘actual_arg_types’ may be used uninitialized in clauses.c Nathan Bossart
  • Re: PG19beta1: GCC 16.1.1 warning: ‘actual_arg_types’ may be used uninitialized in clauses.c Erik Rijkers
  • AW: PG19beta1: GCC 16.1.1 warning: ‘actual_arg_types’ may be used uninitialized in clauses.c Hans Buschmann
  • Re: AW: PG19beta1: GCC 16.1.1 warning: ‘actual_arg_types’ may be used uninitialized in clauses.c Nathan Bossart
  • Re: AW: PG19beta1: GCC 16.1.1 warning: ‘actual_arg_types’ may be used uninitialized in clauses.c Álvaro Herrera
  • Re: AW: PG19beta1: GCC 16.1.1 warning: ‘actual_arg_types’ may be used uninitialized in clauses.c Nathan Bossart
• Re: Optional skipping of unchanged relations during ANALYZE? Ilia Evdokimov
• Re: Type assertions without GCC builtins Jelte Fennema-Nio
  • Re: Type assertions without GCC builtins Peter Eisentraut
  • Re: Type assertions without GCC builtins Tom Lane
• Re: Adding basic NUMA awareness Jakub Wartak
  • Re: Adding basic NUMA awareness Jakub Wartak
  • Re: Adding basic NUMA awareness Tomas Vondra
  • Re: Adding basic NUMA awareness Jakub Wartak
  • Re: Adding basic NUMA awareness Jakub Wartak
  • Re: Adding basic NUMA awareness Jakub Wartak
• Re: Change copyObject() to use typeof_unqual Robins Tharakan
  • Re: Change copyObject() to use typeof_unqual Jelte Fennema-Nio
• Re: Heads Up: cirrus-ci is shutting down June 1st Nazir Bilal Yavuz
  • Re: Heads Up: cirrus-ci is shutting down June 1st Nazir Bilal Yavuz
  • Re: Heads Up: cirrus-ci is shutting down June 1st Tatsuo Ishii
  • Re: Heads Up: cirrus-ci is shutting down June 1st Thomas Munro
  • Re: Heads Up: cirrus-ci is shutting down June 1st Andres Freund
  • Re: Heads Up: cirrus-ci is shutting down June 1st Jacob Champion
  • Re: Heads Up: cirrus-ci is shutting down June 1st Henson Choi
  • Re: Heads Up: cirrus-ci is shutting down June 1st Thomas Munro
  • Re: Heads Up: cirrus-ci is shutting down June 1st Andres Freund
• Re: [PATCH] Preserve replication origin OIDs in pg_upgrade Ajin Cherian
  • Re: [PATCH] Preserve replication origin OIDs in pg_upgrade Nisha Moond
  • Re: [PATCH] Preserve replication origin OIDs in pg_upgrade Nisha Moond
  • Re: [PATCH] Preserve replication origin OIDs in pg_upgrade shveta malik
  • Re: [PATCH] Preserve replication origin OIDs in pg_upgrade Shlok Kyal
  • Re: [PATCH] Preserve replication origin OIDs in pg_upgrade Rui Zhao
  • Re: [PATCH] Preserve replication origin OIDs in pg_upgrade Ajin Cherian
  • Re: [PATCH] Preserve replication origin OIDs in pg_upgrade Rui Zhao
  • Re: [PATCH] Preserve replication origin OIDs in pg_upgrade shveta malik
  • Re: [PATCH] Preserve replication origin OIDs in pg_upgrade shveta malik
  • Re: [PATCH] Preserve replication origin OIDs in pg_upgrade Shlok Kyal
  • Re: [PATCH] Preserve replication origin OIDs in pg_upgrade Zsolt Parragi
  • Re: [PATCH] Preserve replication origin OIDs in pg_upgrade Ajin Cherian
  • Re: [PATCH] Preserve replication origin OIDs in pg_upgrade Rui Zhao
  • Re: [PATCH] Preserve replication origin OIDs in pg_upgrade shveta malik
  • Re: [PATCH] Preserve replication origin OIDs in pg_upgrade shveta malik
  • Re: [PATCH] Preserve replication origin OIDs in pg_upgrade Shlok Kyal
  • Re: [PATCH] Preserve replication origin OIDs in pg_upgrade Rui Zhao
  • Re: [PATCH] Preserve replication origin OIDs in pg_upgrade shveta malik
  • Re: [PATCH] Preserve replication origin OIDs in pg_upgrade shveta malik
  • RE: [PATCH] Preserve replication origin OIDs in pg_upgrade Hayato Kuroda (Fujitsu)
  • Re: [PATCH] Preserve replication origin OIDs in pg_upgrade shveta malik
  • Re: [PATCH] Preserve replication origin OIDs in pg_upgrade Amit Kapila
  • RE: [PATCH] Preserve replication origin OIDs in pg_upgrade Hayato Kuroda (Fujitsu)
  • Re: [PATCH] Preserve replication origin OIDs in pg_upgrade Amit Kapila
  • Re: [PATCH] Preserve replication origin OIDs in pg_upgrade shveta malik
  • Re: [PATCH] Preserve replication origin OIDs in pg_upgrade Ajin Cherian
  • Re: [PATCH] Preserve replication origin OIDs in pg_upgrade shveta malik
  • Re: [PATCH] Preserve replication origin OIDs in pg_upgrade Shlok Kyal
  • Re: [PATCH] Preserve replication origin OIDs in pg_upgrade Ajin Cherian
  • Re: [PATCH] Preserve replication origin OIDs in pg_upgrade shveta malik
  • Re: [PATCH] Preserve replication origin OIDs in pg_upgrade shveta malik
  • Re: [PATCH] Preserve replication origin OIDs in pg_upgrade Amit Kapila
• Re: [Bug Report + Patch] File descriptor leak when io_method=io_uring Lucas DRAESCHER
• Re: [PATCH] Fix replica identity mismatch for partitioned tables with publish_via_partition_root jihyun bahn
  • Re: [PATCH] Fix replica identity mismatch for partitioned tables with publish_via_partition_root Henson Choi
• btree_gist: Fix NaN handling in float4 and float8 opclasses Ewan Young
  • Re: btree_gist: Fix NaN handling in float4 and float8 opclasses Tender Wang
  • Re: btree_gist: Fix NaN handling in float4 and float8 opclasses Ewan Young
• DataChecksumsStateStruct cost_delay fields and locking Heikki Linnakangas
  • Re: DataChecksumsStateStruct cost_delay fields and locking Daniel Gustafsson
  • Re: DataChecksumsStateStruct cost_delay fields and locking Heikki Linnakangas
  • Re: DataChecksumsStateStruct cost_delay fields and locking Daniel Gustafsson
• Re: proposal - queryid can be used as filter for auto_explain Pavel Stehule
  • Re: proposal - queryid can be used as filter for auto_explain Jakub Wartak
  • Re: proposal - queryid can be used as filter for auto_explain Pavel Stehule
  • Re: proposal - queryid can be used as filter for auto_explain Zsolt Parragi
  • Re: proposal - queryid can be used as filter for auto_explain Pavel Stehule
  • Re: proposal - queryid can be used as filter for auto_explain Zsolt Parragi
  • Re: proposal - queryid can be used as filter for auto_explain Pavel Stehule
  • Re: proposal - queryid can be used as filter for auto_explain Kyotaro Horiguchi
  • Re: proposal - queryid can be used as filter for auto_explain Pavel Stehule
  • Re: proposal - queryid can be used as filter for auto_explain Zsolt Parragi
  • Re: proposal - queryid can be used as filter for auto_explain Pavel Stehule
  • Re: proposal - queryid can be used as filter for auto_explain Kyotaro Horiguchi
  • Re: proposal - queryid can be used as filter for auto_explain Pavel Stehule
  • Re: proposal - queryid can be used as filter for auto_explain Kyotaro Horiguchi
  • Re: proposal - queryid can be used as filter for auto_explain Pavel Stehule
• Re: Fix race in ReplicationSlotRelease for ephemeral slots Xuneng Zhou
  • Re: Fix race in ReplicationSlotRelease for ephemeral slots Xuneng Zhou
  • Re: Fix race in ReplicationSlotRelease for ephemeral slots Amit Kapila
  • Re: Fix race in ReplicationSlotRelease for ephemeral slots Xuneng Zhou
  • Re: Fix race in ReplicationSlotRelease for ephemeral slots Amit Kapila
  • Re: Fix race in ReplicationSlotRelease for ephemeral slots Xuneng Zhou
  • Re: Fix race in ReplicationSlotRelease for ephemeral slots Amit Kapila
  • Re: Fix race in ReplicationSlotRelease for ephemeral slots Amit Kapila
  • Re: Fix race in ReplicationSlotRelease for ephemeral slots Xuneng Zhou
• Re: Support EXCEPT for ALL SEQUENCES publications Peter Smith
  • Re: Support EXCEPT for ALL SEQUENCES publications Shlok Kyal
  • Re: Support EXCEPT for ALL SEQUENCES publications Peter Smith
  • Re: Support EXCEPT for ALL SEQUENCES publications Peter Smith
  • Re: Support EXCEPT for ALL SEQUENCES publications Shlok Kyal
  • Re: Support EXCEPT for ALL SEQUENCES publications Peter Smith
  • Re: Support EXCEPT for ALL SEQUENCES publications shveta malik
  • Re: Support EXCEPT for ALL SEQUENCES publications Shlok Kyal
  • Re: Support EXCEPT for ALL SEQUENCES publications shveta malik
  • Re: Support EXCEPT for ALL SEQUENCES publications Peter Smith
  • Re: Support EXCEPT for ALL SEQUENCES publications shveta malik
  • Re: Support EXCEPT for ALL SEQUENCES publications Shlok Kyal
  • Re: Support EXCEPT for ALL SEQUENCES publications Peter Smith
  • Re: Support EXCEPT for ALL SEQUENCES publications Shlok Kyal
  • Re: Support EXCEPT for ALL SEQUENCES publications Ashutosh Sharma
  • Re: Support EXCEPT for ALL SEQUENCES publications Peter Smith
  • Re: Support EXCEPT for ALL SEQUENCES publications Ashutosh Sharma
  • Re: Support EXCEPT for ALL SEQUENCES publications Ashutosh Sharma
  • Re: Support EXCEPT for ALL SEQUENCES publications Peter Smith
  • Re: Support EXCEPT for ALL SEQUENCES publications Peter Smith
  • Re: Support EXCEPT for ALL SEQUENCES publications shveta malik
  • Re: Support EXCEPT for ALL SEQUENCES publications solai v
• 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 vignesh C
  • 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 Nisha Moond
  • 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 Amit Kapila
  • Re: Proposal: Conflict log history table for Logical Replication vignesh C
  • 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 shveta malik
  • 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 Amit Kapila
  • 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 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 vignesh C
  • 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 Shlok Kyal
  • 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 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 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 Peter Smith
  • 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 shveta malik
  • Re: Proposal: Conflict log history table for Logical Replication Amit Kapila
  • Re: Proposal: Conflict log history table for Logical Replication Shlok Kyal
  • 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 Shlok Kyal
  • 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 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 Robert Haas
  • Re: Proposal: Conflict log history table for Logical Replication Amit Kapila
  • Re: Proposal: Conflict log history table for Logical Replication Robert Haas
  • Re: Proposal: Conflict log history table for Logical Replication Amit Kapila
  • Re: Proposal: Conflict log history table for Logical Replication Kedar Anavardekar
  • 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 Dilip Kumar
  • Re: Proposal: Conflict log history table for Logical Replication shveta malik
  • Re: Proposal: Conflict log history table for Logical Replication Amit Kapila

• Earlier messages
• Later messages