pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Rory Campbell-Lange <rory@campbell-lange.net>
To: pgsql-performance@lists.postgresql.org
Subject: Re: data consolidation: logical replication design considerations
Date: Sat, 23 Jul 2022 09:40:23 +0100
Message-ID: <Ytuz97ao+5iIwomc@campbell-lange.net> (raw)
In-Reply-To: <YtLiLaDdvhQk9ZzB@campbell-lange.net>
References: <YtLiLaDdvhQk9ZzB@campbell-lange.net>

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





view thread (4+ messages)

Message-ID: <Ytuz97ao+5iIwomc@campbell-lange.net>
Permalink:  ../Ytuz97ao+5iIwomc@campbell-lange.net/
Also on:    postgresql.org/message-id/Ytuz97ao+5iIwomc@campbell-lange.net

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-performance@postgresql.org
  Cc: rory@campbell-lange.net, pgsql-performance@lists.postgresql.org
  Subject: Re: data consolidation: logical replication design considerations
  In-Reply-To: <Ytuz97ao+5iIwomc@campbell-lange.net>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox