Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.96) (envelope-from ) id 1vfqSh-005RUM-1k for pgsql-hackers@arkaria.postgresql.org; Wed, 14 Jan 2026 02:18:20 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.96) (envelope-from ) id 1vfqSg-007UkS-14 for pgsql-hackers@arkaria.postgresql.org; Wed, 14 Jan 2026 02:18:18 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.96) (envelope-from ) id 1vfqSf-007UkJ-3A for pgsql-hackers@lists.postgresql.org; Wed, 14 Jan 2026 02:18:18 +0000 Received: from mail-qt1-x82f.google.com ([2607:f8b0:4864:20::82f]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.96) (envelope-from ) id 1vfqSe-000KtW-0g for pgsql-hackers@lists.postgresql.org; Wed, 14 Jan 2026 02:18:17 +0000 Received: by mail-qt1-x82f.google.com with SMTP id d75a77b69052e-4ee257e56aaso5060991cf.0 for ; Tue, 13 Jan 2026 18:18:14 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1768357093; x=1768961893; darn=lists.postgresql.org; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=UTRfzxKDRvuoGAdX9G6PmXZzRdtUWJB6+x0XNISZCjo=; b=CcGxV5sELNajC8lsv6zL3KEg1vgq9QgwAauLe+dZcF21NfBc34Kuy9CpeE0VaksvSf jei5dnx9rGv5twTqPpQG7s/UE7C9XkhK24w2vf4qQa8jryLM3PdW71ceir6jBvQjVLWW RGEBPSo0gybsLLLeHBA2kcHXIubcE75XbM1GIiCxu5gW/fOTuTbdKGMGp0OEA3PwdOia PvOjNB7U9MwKoum/gstIyWYzLd1fbgC3WkFxy37B+KdVx3+a9ak95qyekAtYNkzdZ2TD R2pW0/QPm2K1lXic/N9y6tPoa86ALlOsOHr3AsDhI646Q3wlqghKE0eGUZpP37J1YRq2 jMWg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1768357093; x=1768961893; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-gg:x-gm-message-state:from:to:cc:subject:date :message-id:reply-to; bh=UTRfzxKDRvuoGAdX9G6PmXZzRdtUWJB6+x0XNISZCjo=; b=HkbC5MyTLFHh5oLhaI9QYxrY+k/SaPN1duDyvVUTPX0E/VfkmJmjZlW0Y1A6cnmuv+ jem6k7qCKIHxtTFGFtp3miIKpCsZwUZ1s3fNhUHYdN51MUUzhB0/NdaoVQV6bdCs0zn6 vXfzk2LLjL+SL5T/GZnqItWD5lYzGKPRxMB676/VeEvtyROGhhboDb6sByG6yYpNaq24 Frvm8OQvBhaJVpURxkmnJsTbz0ttyMilvG69x5wGckeLkcrr9fXUjNXXnurGpMy7j2Vd ObetRBMDKuTyUe307u5TY7oY4Pij2YcGkNcRZ6li/ukIO6eh090dmuLuQwA0sH2OWT2W Mfzw== X-Forwarded-Encrypted: i=1; AJvYcCVaSYdZGl8D2sZ8uo2Idh1v2rsqn50X5jTz9iPZaJK2n5c3w3We3yxvt0pqC2Gbv5d5tGaH0/NJVNHJnGpM@lists.postgresql.org X-Gm-Message-State: AOJu0YxLaFbGxmHG8qCtXO3ZZW0tS09Ziw7jnCwiefYurw3oNzQ0McDs 57ftR0at7qle9joap5fUB9HSQfRVoRYI50jjw/bqno59g1q1tmCSTJeuJ+B0xCj8ZkSoou8vleU az9VQ7KXaODkOUHgpuJ5fpfr+x1ArHQ4= X-Gm-Gg: AY/fxX5A3mxMyN/SQmXRFQMUtdqGqKPZZUjpOoF74pB9Ao6uQr9PuIt1n0ggy5hJ6uG ad2Oc8Pnefza0ajn/gvinx4ySwzHDXnhLqbHi+TEgHCBH+B9rqyDBuMLg0e+cH7nEsSNaYHIqIo MjQlHtMbpTeolwvuf+q2KeEVHAq+pq2FOTQt+w9X6R7zfshy8BmzrrfB0e5hAWyDsNeA9V7Z69I mUGi/UzNZNffNBPxoPDj1ZNb391SDjwCDd7yrvuMH/47AMpfsmRE2Y8+JQIfwDegyqqy67GwcT6 U/bCJEKs+q1m/MFrfWmLXEyVv9Ubiw== X-Received: by 2002:a05:622a:4d09:b0:4ff:970f:1b5d with SMTP id d75a77b69052e-501487de365mr16016951cf.22.1768357093121; Tue, 13 Jan 2026 18:18:13 -0800 (PST) MIME-Version: 1.0 References: In-Reply-To: From: Peter Smith Date: Wed, 14 Jan 2026 13:17:45 +1100 X-Gm-Features: AZwV_QgXO3VpISkfqOoDyBRhYrJRUA-EU_wA5iQR4W18HaOxsltroov8P20REtw Message-ID: Subject: Re: Proposal: Conflict log history table for Logical Replication To: Dilip Kumar Cc: vignesh C , shveta malik , Amit Kapila , Masahiko Sawada , Bharath Rupireddy , PostgreSQL Hackers Content-Type: text/plain; charset="UTF-8" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk Some review comments for patch v21-0003. ====== (v21-0003 is identical to v20-0003. None of my v20-0003 review comments have been addressed yet.) ~~~ Anyway, here is one more review comment: 1. The DOCS for CREATE SUBSCRIPTION say: + pg_conflict schema. This allows for easy querying and + analysis of conflicts. This table is automatically dropped when the + subscription is removed. The DOCS for ALTER SUBSCRIPTION also say: + exist. Conversely, if the destination is changed to + log, logging to the table stops and the internal + table is automatically dropped. ~ I felt these topics about the CLT auto-removal need to be more prominent, like in a note or something similar, to recommend that the user must make a *backup* of the CLT first, if they intend to do post-mortem analysis of the conflict. Maybe the best place to put this is in the CREATE SUBSCRIPTION / Parameters / conflict_log_desttination = table section. IMO "post-mortem" implies first dropping the subscription (e.g. because it might be in some kind of apply retry-loop conflicting over and over and over), and then studying the logs/CLT to figure out where it went wrong. Therefore, it would be bad if the user wants to exactly that kind of study, only to find that they've accidentally also deleted all the CLT evidence when they dropped the subscription. ====== Kind Regards, Peter Smith. Fujitsu Australia