On Wed, Nov 26, 2025 at 2:26 PM Adrian Klaver
wrote:
> On 11/25/25 23:27, Andrew wrote:
> > Hi,
> >
> > I’m using Postgres 17 and the latest versions of repmgr and barman
> >
> > 1. I’m replicating my database to another node using streaming
> replication. wal_level=replica, hot_standby=on.
> > 2
On 11/25/25 23:27, Andrew wrote:
Hi,
I’m using Postgres 17 and the latest versions of repmgr and barman
1. I’m replicating my database to another node using streaming replication.
wal_level=replica, hot_standby=on.
2. I’ve got barman running on the primary node locally and have setup the
barm
Hi,
I’m using Postgres 17 and the latest versions of repmgr and barman
1. I’m replicating my database to another node using streaming replication.
wal_level=replica, hot_standby=on.
2. I’ve got barman running on the primary node locally and have setup the
barman config for streaming replicatio
On 11/25/25 05:46, Andrew wrote:
Hi,
New to the list. If I’m Using streaming archiving with repmgr, and streaming
archiving with barman, do I still need to maintain my archive command, and have
processes in place to delete archived wals periodically? Or are they in effect
defunct due to wal
On 10/21/21 16:23, Rory Falloon wrote:
Hi,
My postgres server setup is thus: a production database, which is
using WAL streaming (hot standby) to four other hosts of various
latencies. I Have a table that is ~200GB which has been backed up, and
now I Want to remove it. The table is not in u
