> On Nov 4, 2021, at 12:16, Alanoly Andrews wrote:
>
> Thanks, Ninad, for the response.
> So, am I to understand that when there is a long-running query on the
> subscriber, the vacuumed data updates from the publisher are held over on the
> subscriber until the query completes? If so, where
disk space (either on the publisher or on the
subscriber)?
Regards.
Alanoly Andrews.
From: Ninad Shah [mailto:nshah.postg...@gmail.com]
Sent: Thursday, November 4, 2021 2:20 PM
To: Alanoly Andrews
Cc: pgsql-general@lists.postgresql.org
Subject: Re: Streaming replication versus Logical replication
Yes, it is going to resolve the issue because streaming is completely a
slave(with few exceptions). Even the VACUUM operation gets replicated
through the master, which is not a case with logical replication. In
logical replication, only data from a few tables gets replicated. In terms
of database a
We are currently running some long-running SELECT queries on the replication
database in a streaming replication pair. Some of these queries can run for 1
hour or more. To avoid errors related to "data no more being available" on the
replication due to vacuuming of old data on the primary databa
