Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1oIxPM-0006vy-Hq for pgsql-performance@arkaria.postgresql.org; Tue, 02 Aug 2022 19:18:24 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1oIxPL-0007b6-E5 for pgsql-performance@arkaria.postgresql.org; Tue, 02 Aug 2022 19:18:23 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1oIxPK-0007aQ-Ro for pgsql-performance@lists.postgresql.org; Tue, 02 Aug 2022 19:18:23 +0000 Received: from campbell-lange.net ([178.79.140.51]) by makus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1oIxPI-0000TZ-5W for pgsql-performance@postgresql.org; Tue, 02 Aug 2022 19:18:21 +0000 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=campbell-lange.net; s=it; h=In-Reply-To:Content-Type:MIME-Version: References:Message-ID:Subject:Cc:To:From:Date:Sender:Reply-To: Content-Transfer-Encoding:Content-ID:Content-Description:Resent-Date: Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:List-Id: List-Help:List-Unsubscribe:List-Subscribe:List-Post:List-Owner:List-Archive; bh=eaANMoA9Spl13sChCDtQqEqKCp2N5ceUhbB7RBXCGQA=; b=RjLZxtzv+444MEjU5ARxSg8jwJ w2RFPTKsBHmb247wNh9onC3Ez06BK0Rs17+PZgGkewjEp0EL+Pxi/2Q0JtsWyHUMQUKfpI/D7Yk3N SMNYKO9I1yvzVX98gp/XI7MIjz9P+cup5xmAPvYJZb5o3LFIU+ld0o/KFIVzAxQ29iHM=; Received: from arennes-651-1-229-47.w90-32.abo.wanadoo.fr ([90.32.108.47] helo=rory-t470s) by campbell-lange.net with esmtpsa (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1oIxPF-0078NZ-CE; Tue, 02 Aug 2022 19:18:17 +0000 Received: from rory by rory-t470s with local (Exim 4.94.2) (envelope-from ) id 1oIxPE-002dOp-Kz; Tue, 02 Aug 2022 20:18:16 +0100 Date: Tue, 2 Aug 2022 20:18:16 +0100 From: Rory Campbell-Lange To: Robert Blayzor Cc: pgsql-performance@postgresql.org Subject: Re: PgSQL 14 - Logical Rep - Single table multiple publications? Message-ID: References: <3d5996ac-a181-21a5-62a0-1cd34e6b3f1a@inoc.net> <8bd0f6cd-cbfc-2033-431c-d4ac613c1878@inoc.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <8bd0f6cd-cbfc-2033-431c-d4ac613c1878@inoc.net> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On 02/08/22, Robert Blayzor (rblayzor.bulk@inoc.net) wrote: > On 8/2/22 10:57, Rory Campbell-Lange wrote: > > Special care must be taken with the "replica identity" of published > > tables, as set out at > > https://www.postgresql.org/docs/current/logical-replication-publication.html. > > We would literally just be merging bulk data rows that are considered > immutable, meaning they would never be updated or deleted. We would > replicate only inserts, not deletes, updates, etc. > > Would the table identifier still be required in this case? On the page referenced above is the following: "INSERT operations can proceed regardless of any replica identity." So you should be good. Rory