pgsql-hackers  

Messages by Thread

• • 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 Amit Kapila
  • 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 Nisha Moond
  • 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 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
• Bug in logical decoding with DDL and subtransactions Mark Dilger
• Re: let ALTER TABLE DROP COLUMN drop whole-row referenced object lakshmi
  • Re: let ALTER TABLE DROP COLUMN drop whole-row referenced object jian he
• Re: [PATCH] Fix stale relation close in sequence synchronization vignesh C
  • Re: [PATCH] Fix stale relation close in sequence synchronization Ayush Tiwari
  • Re: [PATCH] Fix stale relation close in sequence synchronization vignesh C
  • Re: [PATCH] Fix stale relation close in sequence synchronization Ayush Tiwari
  • Re: [PATCH] Fix stale relation close in sequence synchronization Amit Kapila
  • Re: [PATCH] Fix stale relation close in sequence synchronization Ajin Cherian
  • Re: [PATCH] Fix stale relation close in sequence synchronization vignesh C
  • Re: [PATCH] Fix stale relation close in sequence synchronization Ayush Tiwari
  • Re: [PATCH] Fix stale relation close in sequence synchronization vignesh C
  • Re: [PATCH] Fix stale relation close in sequence synchronization Ayush Tiwari
  • Re: [PATCH] Fix stale relation close in sequence synchronization Amit Kapila
• Re: Bug in ALTER SUBSCRIPTION ... SERVER / ... CONNECTION with broken old server Chao Li
  • Re: Bug in ALTER SUBSCRIPTION ... SERVER / ... CONNECTION with broken old server Ajin Cherian
  • Re: Bug in ALTER SUBSCRIPTION ... SERVER / ... CONNECTION with broken old server Chao Li
  • Re: Bug in ALTER SUBSCRIPTION ... SERVER / ... CONNECTION with broken old server Zsolt Parragi
  • Re: Bug in ALTER SUBSCRIPTION ... SERVER / ... CONNECTION with broken old server Chao Li
  • Re: Bug in ALTER SUBSCRIPTION ... SERVER / ... CONNECTION with broken old server Jeff Davis
  • Re: Bug in ALTER SUBSCRIPTION ... SERVER / ... CONNECTION with broken old server Chao Li
  • Re: Bug in ALTER SUBSCRIPTION ... SERVER / ... CONNECTION with broken old server Jeff Davis
  • Re: Bug in ALTER SUBSCRIPTION ... SERVER / ... CONNECTION with broken old server Chao Li
  • Re: Bug in ALTER SUBSCRIPTION ... SERVER / ... CONNECTION with broken old server Jeff Davis
  • Re: Bug in ALTER SUBSCRIPTION ... SERVER / ... CONNECTION with broken old server Chao Li
  • Re: Bug in ALTER SUBSCRIPTION ... SERVER / ... CONNECTION with broken old server Amit Kapila
• Re: Fix race condition in pg_get_publication_tables with concurrent DROP TABLE Chao Li
  • Re: Fix race condition in pg_get_publication_tables with concurrent DROP TABLE Bharath Rupireddy
  • Re: Fix race condition in pg_get_publication_tables with concurrent DROP TABLE shveta malik
  • Re: Fix race condition in pg_get_publication_tables with concurrent DROP TABLE Chao Li
  • Re: Fix race condition in pg_get_publication_tables with concurrent DROP TABLE shveta malik
  • Re: Fix race condition in pg_get_publication_tables with concurrent DROP TABLE Chao Li
  • Re: Fix race condition in pg_get_publication_tables with concurrent DROP TABLE Bharath Rupireddy
  • Re: Fix race condition in pg_get_publication_tables with concurrent DROP TABLE Masahiko Sawada
• Re: Fix race condition in XLogLogicalInfo and ProcSignal initialization. Chao Li
  • Re: Fix race condition in XLogLogicalInfo and ProcSignal initialization. Masahiko Sawada
  • Re: Fix race condition in XLogLogicalInfo and ProcSignal initialization. Chao Li
  • Re: Fix race condition in XLogLogicalInfo and ProcSignal initialization. Masahiko Sawada
  • Re: Fix race condition in XLogLogicalInfo and ProcSignal initialization. Masahiko Sawada
• Re: Fix HAVING-to-WHERE pushdown with nondeterministic collations Richard Guo
  • Re: Fix HAVING-to-WHERE pushdown with nondeterministic collations Richard Guo
  • Re: Fix HAVING-to-WHERE pushdown with nondeterministic collations SATYANARAYANA NARLAPURAM
  • Re: Fix HAVING-to-WHERE pushdown with nondeterministic collations Richard Guo
• Re: Fix the error hint message and test for reset_shared with unknown stats type Michael Paquier
• Re: [PATCH] DISTINCT in plain aggregate window functions Haibo Yan
• Re: Experimenting with wider Unicode storage Thomas Munro
• Re: Pgbench: remove synchronous prepare Robert Haas
  • Re: Pgbench: remove synchronous prepare Dmitrii Bondar
  • Re: Pgbench: remove synchronous prepare Robert Haas
• Re: [PATCH] Fix: Partitioned parent index remains invalid after child indexes are repaired Mohamed ALi
  • Re: [PATCH] Fix: Partitioned parent index remains invalid after child indexes are repaired Michael Paquier
• deep copy with mutation? Robert Haas
  • Re: deep copy with mutation? Ashutosh Bapat
  • Re: deep copy with mutation? David Rowley
• Re: [Patch]Add Graph* node support to expression_tree_mutator Robert Haas
  • Re: [Patch]Add Graph* node support to expression_tree_mutator Ashutosh Bapat
  • Re: [Patch]Add Graph* node support to expression_tree_mutator Peter Eisentraut
  • Re: [Patch]Add Graph* node support to expression_tree_mutator Ashutosh Bapat
• Re: Startup process deadlock: WaitForProcSignalBarriers vs aux process Alexander Lakhin
  • Re: Startup process deadlock: WaitForProcSignalBarriers vs aux process Masahiko Sawada
  • Re: Startup process deadlock: WaitForProcSignalBarriers vs aux process Alexander Lakhin
  • Re: Startup process deadlock: WaitForProcSignalBarriers vs aux process Masahiko Sawada
  • Re: Startup process deadlock: WaitForProcSignalBarriers vs aux process Masahiko Sawada
  • Re: Startup process deadlock: WaitForProcSignalBarriers vs aux process Matthias van de Meent
  • Re: Startup process deadlock: WaitForProcSignalBarriers vs aux process Masahiko Sawada
• Spurious warnings in crypto-des.c when building with gcc-16 -O3 Andres Freund
  • Re: Spurious warnings in crypto-des.c when building with gcc-16 -O3 Ayush Tiwari
  • Re: Spurious warnings in crypto-des.c when building with gcc-16 -O3 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
• Limit GRAPH_TABLE path combinations to prevent memory exhaustion SATYANARAYANA NARLAPURAM
  • Re: Limit GRAPH_TABLE path combinations to prevent memory exhaustion Ashutosh Bapat
  • Re: Limit GRAPH_TABLE path combinations to prevent memory exhaustion SATYANARAYANA NARLAPURAM
• Bogus recovery conflicts due to outdated XLogReceiptTime Andres Freund
• [PATCH] Free BufFile metadata in close and append paths DaeMyung Kang
  • Re: [PATCH] Free BufFile metadata in close and append paths Michael Paquier
• Re: pg_get__*_ddl consolidation Andrew Dunstan
• Making the ENUM operators LEAKPROOF Laurenz Albe
  • Re: Making the ENUM operators LEAKPROOF Laurenz Albe
• [PATCH] Fix EINTR retry condition in pg_flush_data sync_file_range path. DaeMyung Kang
  • Re: [PATCH] Fix EINTR retry condition in pg_flush_data sync_file_range path. Michael Paquier
• Re: [PATCH] Resolve unknown-type literals in GRAPH_TABLE COLUMNS Ashutosh Bapat
  • Re: [PATCH] Resolve unknown-type literals in GRAPH_TABLE COLUMNS Peter Eisentraut
  • Re: [PATCH] Resolve unknown-type literals in GRAPH_TABLE COLUMNS Ashutosh Bapat
• Re: [PATCH] Improve error message for graph variable references in subqueries within GRAPH_TABLE Ashutosh Bapat
• Re: [BUG?] macOS (Intel) build warnings: "ranlib: file … has no symbols" for aarch64 objects Tom Lane
  • Re: [BUG?] macOS (Intel) build warnings: "ranlib: file … has no symbols" for aarch64 objects Nathan Bossart
  • Re: [BUG?] macOS (Intel) build warnings: "ranlib: file … has no symbols" for aarch64 objects Nathan Bossart
  • Re: [BUG?] macOS (Intel) build warnings: "ranlib: file … has no symbols" for aarch64 objects Tom Lane
  • Re: [BUG?] macOS (Intel) build warnings: "ranlib: file … has no symbols" for aarch64 objects Nathan Bossart
• Re: Add pg_stat_vfdcache view for VFD cache statistics KAZAR Ayoub
  • Re: Add pg_stat_vfdcache view for VFD cache statistics David Geier
• Re: [Bug][patch]: After dropping the last label from a property graph element, invoking pg_get_propgraphdef() triggers an assertion failure Chao Li
  • Re: [Bug][patch]: After dropping the last label from a property graph element, invoking pg_get_propgraphdef() triggers an assertion failure Peter Eisentraut
  • Re: [Bug][patch]: After dropping the last label from a property graph element, invoking pg_get_propgraphdef() triggers an assertion failure Chao Li
  • Re: [Bug][patch]: After dropping the last label from a property graph element, invoking pg_get_propgraphdef() triggers an assertion failure Peter Eisentraut
  • Re: [Bug][patch]: After dropping the last label from a property graph element, invoking pg_get_propgraphdef() triggers an assertion failure Ashutosh Bapat
  • Re: [Bug][patch]: After dropping the last label from a property graph element, invoking pg_get_propgraphdef() triggers an assertion failure Ashutosh Bapat
• Re: A very quick observation of dangling pointers in Postgres pathlists Andrei Lepikhov
• Re: Changing the state of data checksums in a running cluster Daniel Gustafsson
  • Re: Changing the state of data checksums in a running cluster Ayush Tiwari
  • Re: Changing the state of data checksums in a running cluster Daniel Gustafsson
  • Re: Changing the state of data checksums in a running cluster SATYANARAYANA NARLAPURAM
  • Re: Changing the state of data checksums in a running cluster Daniel Gustafsson
  • Re: Changing the state of data checksums in a running cluster SATYANARAYANA NARLAPURAM
  • Re: Changing the state of data checksums in a running cluster Daniel Gustafsson
  • Re: Changing the state of data checksums in a running cluster SATYANARAYANA NARLAPURAM
  • Re: Changing the state of data checksums in a running cluster Ayush Tiwari
  • Re: Changing the state of data checksums in a running cluster Daniel Gustafsson
  • Re: Changing the state of data checksums in a running cluster Ayush Tiwari
  • Re: Changing the state of data checksums in a running cluster SATYANARAYANA NARLAPURAM
  • Re: Changing the state of data checksums in a running cluster SATYANARAYANA NARLAPURAM
  • Re: Changing the state of data checksums in a running cluster Ayush Tiwari
  • Re: Changing the state of data checksums in a running cluster Daniel Gustafsson
  • Re: Changing the state of data checksums in a running cluster SATYANARAYANA NARLAPURAM
  • Re: Changing the state of data checksums in a running cluster Tomas Vondra
  • Re: Changing the state of data checksums in a running cluster Daniel Gustafsson
  • Re: Changing the state of data checksums in a running cluster Tomas Vondra
  • Re: Changing the state of data checksums in a running cluster Daniel Gustafsson
  • Re: Changing the state of data checksums in a running cluster Tomas Vondra
• Re: Fix DROP PROPERTY GRAPH "unsupported object class" error Ashutosh Bapat
  • Re: Fix DROP PROPERTY GRAPH "unsupported object class" error Bertrand Drouvot
  • Re: Fix DROP PROPERTY GRAPH "unsupported object class" error Ashutosh Bapat
  • Re: Fix DROP PROPERTY GRAPH "unsupported object class" error Bertrand Drouvot
  • Re: Fix DROP PROPERTY GRAPH "unsupported object class" error Alex Guo
  • Re: Fix DROP PROPERTY GRAPH "unsupported object class" error Michael Paquier
  • Re: Fix DROP PROPERTY GRAPH "unsupported object class" error Peter Eisentraut
  • Re: Fix DROP PROPERTY GRAPH "unsupported object class" error Michael Paquier
  • Re: Fix DROP PROPERTY GRAPH "unsupported object class" error Ashutosh Bapat
  • Re: Fix DROP PROPERTY GRAPH "unsupported object class" error Michael Paquier
  • Re: Fix DROP PROPERTY GRAPH "unsupported object class" error Peter Eisentraut
  • Re: Fix DROP PROPERTY GRAPH "unsupported object class" error Michael Paquier
  • Re: Fix DROP PROPERTY GRAPH "unsupported object class" error Tom Lane
  • Re: Fix DROP PROPERTY GRAPH "unsupported object class" error Ashutosh Bapat
  • Re: Fix DROP PROPERTY GRAPH "unsupported object class" error Tom Lane
  • Re: Fix DROP PROPERTY GRAPH "unsupported object class" error Michael Paquier
  • Re: Fix DROP PROPERTY GRAPH "unsupported object class" error Ashutosh Bapat
  • Re: Fix DROP PROPERTY GRAPH "unsupported object class" error Michael Paquier
  • Re: Fix DROP PROPERTY GRAPH "unsupported object class" error Ashutosh Bapat
  • Re: Fix DROP PROPERTY GRAPH "unsupported object class" error Michael Paquier
• Re: Property graph: fix error handling when dropping non-existent label property Ashutosh Bapat
• Re: Support logical replication of DDLs, take2 Andres Freund
  • Re: Support logical replication of DDLs, take2 Hannu Krosing
  • Re: Support logical replication of DDLs, take2 Masahiko Sawada
  • Re: Support logical replication of DDLs, take2 Amit Kapila
  • Re: Support logical replication of DDLs, take2 Masahiko Sawada
  • Re: Support logical replication of DDLs, take2 Amit Kapila
  • Re: Support logical replication of DDLs, take2 Masahiko Sawada
  • Re: Support logical replication of DDLs, take2 Masahiko Sawada
• Re: Include schema-qualified names in publication error messages. shveta malik
  • Re: Include schema-qualified names in publication error messages. Dilip Kumar
  • Re: Include schema-qualified names in publication error messages. shveta malik
  • Re: Include schema-qualified names in publication error messages. Dilip Kumar
  • Re: Include schema-qualified names in publication error messages. vignesh C
  • Re: Include schema-qualified names in publication error messages. Dilip Kumar
  • Re: Include schema-qualified names in publication error messages. Euler Taveira
  • Re: Include schema-qualified names in publication error messages. Dilip Kumar
  • Re: Include schema-qualified names in publication error messages. shveta malik
  • Re: Include schema-qualified names in publication error messages. Amit Kapila
  • Re: Include schema-qualified names in publication error messages. shveta malik
  • Re: Include schema-qualified names in publication error messages. Dilip Kumar
  • Re: Include schema-qualified names in publication error messages. Amit Kapila
  • Re: Include schema-qualified names in publication error messages. Euler Taveira
  • Re: Include schema-qualified names in publication error messages. Amit Kapila
  • Re: Include schema-qualified names in publication error messages. vignesh C
  • Re: Include schema-qualified names in publication error messages. shveta malik
  • Re: Include schema-qualified names in publication error messages. Amit Kapila
  • Re: Include schema-qualified names in publication error messages. Dilip Kumar
  • Re: Include schema-qualified names in publication error messages. shveta malik
  • Re: Include schema-qualified names in publication error messages. Euler Taveira
  • Re: Include schema-qualified names in publication error messages. Amit Kapila
  • Re: Include schema-qualified names in publication error messages. Euler Taveira
  • Re: Include schema-qualified names in publication error messages. Amit Kapila
  • Re: Include schema-qualified names in publication error messages. Peter Smith
  • Re: Include schema-qualified names in publication error messages. vignesh C
  • Re: Include schema-qualified names in publication error messages. Euler Taveira
  • Re: Include schema-qualified names in publication error messages. vignesh C
  • Re: Include schema-qualified names in publication error messages. Peter Smith

• Later messages