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 <pgsql-performance-owner+archive@lists.postgresql.org>)
	id 1oFAga-0007sK-7X
	for pgsql-performance@arkaria.postgresql.org; Sat, 23 Jul 2022 08:40:32 +0000
Received: from localhost ([127.0.0.1] helo=malur.postgresql.org)
	by malur.postgresql.org with esmtp (Exim 4.92)
	(envelope-from <pgsql-performance-owner+archive@lists.postgresql.org>)
	id 1oFAgX-0005aW-FR
	for pgsql-performance@arkaria.postgresql.org; Sat, 23 Jul 2022 08:40:29 +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 <rory@campbell-lange.net>)
	id 1oFAgW-0005aM-Si
	for pgsql-performance@lists.postgresql.org; Sat, 23 Jul 2022 08:40:29 +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 <rory@campbell-lange.net>)
	id 1oFAgU-0004aP-8L
	for pgsql-performance@lists.postgresql.org; Sat, 23 Jul 2022 08:40:27 +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:To:From:Date:Sender:Reply-To:Cc:
	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=zMf1iQFxOo2pSLEHuy2vM23AAplC/guvv7IYlnWa1UM=; b=B9bgZP49t60sQ8+U2YnPzbICBG
	N6XDOKHXUcvxMZRU0fGT5cFtiVPY99Gb0b8Z3OZcs/kLREghJc8q0Zr7mKxjFrOrfZe3IP0NBZN6T
	FO1GS1YMqRVi+sQKE1IYgeplmoEg7RtJxzNJz+QNhKXfOkukFrmFNpvPGLVYf+9UpcTI=;
Received: from [217.138.52.158] (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 <rory@campbell-lange.net>)
	id 1oFAgR-0067cq-MH
	for pgsql-performance@lists.postgresql.org; Sat, 23 Jul 2022 08:40:23 +0000
Received: from rory by rory-t470s with local (Exim 4.94.2)
	(envelope-from <rory@rory-t470s>)
	id 1oFAgR-0033AX-5p
	for pgsql-performance@lists.postgresql.org; Sat, 23 Jul 2022 09:40:23 +0100
Date: Sat, 23 Jul 2022 09:40:23 +0100
From: Rory Campbell-Lange <rory@campbell-lange.net>
To: pgsql-performance@lists.postgresql.org
Subject: Re: data consolidation: logical replication design considerations
Message-ID: <Ytuz97ao+5iIwomc@campbell-lange.net>
References: <YtLiLaDdvhQk9ZzB@campbell-lange.net>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <YtLiLaDdvhQk9ZzB@campbell-lange.net>
List-Id: <pgsql-performance.lists.postgresql.org>
List-Help: <https://lists.postgresql.org/manage/>
List-Subscribe: <https://lists.postgresql.org/manage/>
List-Post: <mailto:pgsql-performance@lists.postgresql.org>
List-Owner: <mailto:pgsql-performance-owner@lists.postgresql.org>
List-Archive: <https://www.postgresql.org/list/pgsql-performance>
Archived-At: 
 <https://www.postgresql.org/message-id/Ytuz97ao%2B5iIwomc%40campbell-lange.net>
Precedence: bulk

On 16/07/22, Rory Campbell-Lange (rory@campbell-lange.net) wrote:
> I'd be grateful for some comments on the advisability of using a large
> number of concurrent logical replication publications/subscriptions.
> Below I've set out the current environment and a suggested design.
> Apologies for the length of this email.
...
> * to avoid overloading the existing primary host with many replication
>   slots, it would be wise to implement aggregation on another host 

Looking into this further it appears that a streaming replication secondary can
not act as a logical replication publisher. Is that correct?

Rory