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 1wS0bx-002shN-0Y for pgsql-hackers@arkaria.postgresql.org; Tue, 26 May 2026 22:50:57 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.96) (envelope-from ) id 1wS0bv-006Dgs-0K for pgsql-hackers@arkaria.postgresql.org; Tue, 26 May 2026 22:50:56 +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 1wS0bu-006Dgk-2Z for pgsql-hackers@lists.postgresql.org; Tue, 26 May 2026 22:50:55 +0000 Received: from mail-qt1-x82d.google.com ([2607:f8b0:4864:20::82d]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.98.2) (envelope-from ) id 1wS0bt-00000001avA-2oJw for pgsql-hackers@lists.postgresql.org; Tue, 26 May 2026 22:50:55 +0000 Received: by mail-qt1-x82d.google.com with SMTP id d75a77b69052e-516d15ed2bcso48646331cf.0 for ; Tue, 26 May 2026 15:50:53 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1779835852; cv=none; d=google.com; s=arc-20240605; b=Sfy078xi6GHrHXdvRlGshU7v0VtthAMb58LwocLwsAvDiLDogWMxhvn3JpLp1mWOru IGfDgC4h6Ez/RSImuFGXlIXV9ii8JNS27W7qtm6sw/EUVpu0l2NFBKgBxJv9j3ADRUHw PDy29Ng7LFJk3QPkzJdAp9jj7T++P6GCPfr2c5nVKn9Cng2wDnUsvWICx9ou5CQTDeop iVJDoQszt8BNYGaG8wjX/OTpWdFQyxHXBAWvHXudkSMpNAL7G+S6Vlo+ZU3niSa1D5KN Rz61+bILZ3FNM8Js/BH+AvOBMGe99swIJAOcylTtvg9tCz/S0E3YeHWTjB5/s+3vv5nZ wv7Q== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20240605; h=content-transfer-encoding:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:dkim-signature; bh=tlRpmZ1q95FKbc8BsLB+1SK4j1rFfLP5r4wl6iTXAJ4=; fh=eju9trSUeMH7AchGyjLQVsUNvQOub8UGO5nhjPt+Ccc=; b=a0Gro+Xe2MK5zxhQQ4+ESZXyn1eutXfUP6atk9whSSu3zurGNce+EwKVHm92j+fNR5 Em7QVnYgOqDHC7tu4zU1H1akvsDPfhEfvUgIDbWfW2j7aUvo2XArbY5howhMLfJfGfNs ksH60t8m61UxWRsYBrYbTN6jfdzL3WUUcecphjyGKFjPQ3p1vcPRdZz3lNxCXn7Z0sxU NL9OQBAV2qkn9u1Lk9tlRI9XJ3lBQREmK5i2ettim9xqbaZ3+4PKECl9lKpbrmfDfsBD C4c10LzbgGIpcZgHZ3yiq0AFLETL1qQR1MOFk/5V0Zd/nxitgrRhn8XqSj/RdAsBKACl s+Og==; darn=lists.postgresql.org ARC-Authentication-Results: i=1; mx.google.com; arc=none DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20251104; t=1779835852; x=1780440652; darn=lists.postgresql.org; h=content-transfer-encoding:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:from:to:cc:subject:date :message-id:reply-to; bh=tlRpmZ1q95FKbc8BsLB+1SK4j1rFfLP5r4wl6iTXAJ4=; b=UK2gtQtAxpCwW3bxSIgI8QRlix/0YbuWDaYsfb0TA5EFclm0GzvT1PTFNfk+i0ZHd3 h4ZLcoR0YVrn24k015LDv+E6uSS3Wg1ryaT+nIGoCSonbI25/m2JX2Rwdb8osuWm6zJB sPVOBUljiwivt4Anwomgbgj+xdroOeQG0wcwRefdCXBgm8giQuxA30s3Dd6BEcJQzayp zMVIV9bde8yGSN3NQqbaCDbSGNtPtE8X7M60cToU58n8g0aeACUKK+pcdQuxWRUpzK1E sB4VR/GrUUDe3togIjFQIHwcTMuRfNNVlkGhWYNjlJoyp33VnPa5IYPpcLWC4IdCFgsl 305Q== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20251104; t=1779835852; x=1780440652; h=content-transfer-encoding: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=tlRpmZ1q95FKbc8BsLB+1SK4j1rFfLP5r4wl6iTXAJ4=; b=V06q6wIyedzJA8FWng4ETWOzF5QeaxCL4J+jNUPSDmOK2wrwqsoCeOqwrMmHMi8ny3 WesnU98rkUEOOp3x/RLkPwz2icm9gEi02EaOkwBa/ro0YJZzVRFp/iPeb8Z0zJ0lLqYr 4zHzx2m8kr3KYygGzaWWqaZkBrUXKmXE2aUxvWHS/PLOP+XMHtj6uWjV7MxfR/QnTPBq n+yn5LVN7TmizSyhIrS6uKeXRXH3MwvmxDiIoed+XWkw7vSZtSAUTn4YfVos7I/tA+4I H8I0HWFwUtmtFGktk6oUoNQpZH5xuz6SigXKJGbSXci3RyuLDGIW8u6SDtnQOP1IHNjN M/bQ== X-Forwarded-Encrypted: i=1; AFNElJ+dgRsPbpYRVmRKPIUdVTS5MEHeo6Wl0cLR0e5FO28ePfxyu+hC7FopjeG3OrT9zAHd4hjrcXEWEdQZrb66@lists.postgresql.org X-Gm-Message-State: AOJu0Yy6Qt6oUGUAczNk6XayOM61m3qvlh5IzVgMktVpZepJic+SyV/n /f/XT0rIrkcbBd20v+Fx74NHFaZY4aY9NUi8z5D5oo4TGiXOFfQ26PCUvNsNtKocWipDPqZsslI RU/tqjR4bS5q2ozH7kqeO7WrxeRhVuKE= X-Gm-Gg: Acq92OHGds5VEOLLMPUpfD02WwqLvbjmtwsbw90aN/B6VvFo5IJe6kR3RxM9t84fxPM cXhsTeU22KiTDfLOOiid2qbidzFhf9KCW11HcjJyzaNd41HH8cfPpvy4hGta/ouGn/2aJBeOs5/ moWzdXGND5p99zrjFQ8bGNNexb7mpr7fFJm8Dd2CAo1TjBk9p0ZD9DTnpUIloIrBVEer9+VoxTv 4LAGl0OPHnybWty6hWQvFG4/xX+NkfRWdxKvl8+h3SOGZvi3HzQH8c9QEI9vuWiaZOaEOAsZLfX FUoc6FhTXwyY0jKL5A== X-Received: by 2002:a05:622a:188b:b0:516:d7a5:afdd with SMTP id d75a77b69052e-516d7a5b597mr224201611cf.3.1779835852009; Tue, 26 May 2026 15:50:52 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: Peter Smith Date: Wed, 27 May 2026 08:50:23 +1000 X-Gm-Features: AVHnY4LlR4jWuuM4qp3QaTEO9ncqQRlY_Fo9wTBRyY001ipeZ49XBUjXu_dMy4Y Message-ID: Subject: Re: Proposal: Conflict log history table for Logical Replication To: shveta malik Cc: vignesh C , Nisha Moond , Dilip Kumar , Amit Kapila , Masahiko Sawada , Bharath Rupireddy , PostgreSQL Hackers , shveta malik Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On Tue, May 26, 2026 at 7:38=E2=80=AFPM shveta malik wrote: ... > 1) > heap_create: > + errdetail("Conflict schema modifications are currently disallowed."))); > LookupCreationNamespace: > + errmsg("cannot move objects into or out of the pg_conflict schema"))); > > Can we make it same through-out, either we use 'Conflict schema' at > both the places or pg_conflict schema. Since in these 2 functions, in > previous messages, we are using names like 'System catalog', 'TOAST > schema' etc, I think we can use Conflict schema at both the places. > What do others think on this? > The suggested name of "Conflict schema" LGTM. My only concern was that a user may not know where that is referring to. OTOH, things like "System catalog" have 100s of mentions and whole documentation chapters dedicated to them. If we go with "Conflict schema", then the documentation needs to also consistently use that term, describe what it is for, and make it very easy to look up and discover that "Conflict schema" is 'pg_conflict'. Currently (in patches 0008/9) there is very little explanation even about what pg_conflict is, apart from just observing in passing that the CLT gets written to that "dedicated namespace". It seems a bit backwards describing the parent schema by the contents: Instead of saying when there is a CLT it gets written there, IMO it should be the other way around, and say there is a "Conflict schema" which is where the CLTs (if any) reside. =3D=3D=3D=3D=3D=3D Kind Regards, Peter Smith. Fujitsu Australia