public inbox for [email protected]
help / color / mirror / Atom feedusing pgbackrest in a PG streaming replication cfg with repmgr
3+ messages / 2 participants
[nested] [flat]
* using pgbackrest in a PG streaming replication cfg with repmgr
@ 2025-08-26 17:44 Ghiurea, Isabella <[email protected]>
2025-08-26 18:50 ` Re: using pgbackrest in a PG streaming replication cfg with repmgr Ron Johnson <[email protected]>
2025-08-26 18:56 ` Re: using pgbackrest in a PG streaming replication cfg with repmgr Ron Johnson <[email protected]>
0 siblings, 2 replies; 3+ messages in thread
From: Ghiurea, Isabella @ 2025-08-26 17:44 UTC (permalink / raw)
To: pgsql-admin
Hi List,
We have a requirement to start using pgbackrest for db backups on slave PG hosts already configured in Streaming Replication . To avoid any issues with WAL files transfer and performance in existing PG streaming replication configuration , we plan to run pgbackrest only at a slave host and only full database backups ( no need for PITR/incremental when already have synchronous replication) . My questions are :
-How do I cfg pgbackrest to not archive/use WAL files without affecting the synchronous streaming replication?
- Are any known issues with pgbackrest + repmgr when running : repmgr standby switchover ?( to promote a new db master while slave is online ) or repmgr promote ?
thank you !!!
^ permalink raw reply [nested|flat] 3+ messages in thread
* Re: using pgbackrest in a PG streaming replication cfg with repmgr
2025-08-26 17:44 using pgbackrest in a PG streaming replication cfg with repmgr Ghiurea, Isabella <[email protected]>
@ 2025-08-26 18:50 ` Ron Johnson <[email protected]>
1 sibling, 0 replies; 3+ messages in thread
From: Ron Johnson @ 2025-08-26 18:50 UTC (permalink / raw)
To: pgsql-admin
On Tue, Aug 26, 2025 at 1:45 PM Ghiurea, Isabella <
[email protected]> wrote:
> no need for PITR/incremental when already have synchronous replication
>
What happens when you take backups on Sundays, today is Tuesday, but you
need the state of the database as it was on Monday at 09:00?
Remember: replication is not a backup!!
--
Death to <Redacted>, and butter sauce.
Don't boil me, I'm still alive.
<Redacted> lobster!
^ permalink raw reply [nested|flat] 3+ messages in thread
* Re: using pgbackrest in a PG streaming replication cfg with repmgr
2025-08-26 17:44 using pgbackrest in a PG streaming replication cfg with repmgr Ghiurea, Isabella <[email protected]>
@ 2025-08-26 18:56 ` Ron Johnson <[email protected]>
1 sibling, 0 replies; 3+ messages in thread
From: Ron Johnson @ 2025-08-26 18:56 UTC (permalink / raw)
To: Pgsql-admin <[email protected]>
On Tue, Aug 26, 2025 at 1:45 PM Ghiurea, Isabella <
[email protected]> wrote:
> and only full database backups
>
If you only want to do full backups, then use pg_dump on the replica
server. Might need to adjust parameters like max_standby_streaming_delay
and hot_standby_feedbac, just like for long-running queries on the replica.
https://www.postgresql.org/docs/16/runtime-config-replication.html
<https://www.postgresql.org/docs/16/runtime-config-replication.html#GUC-MAX-STANDBY-STREAMING-DELAY;
--
Death to <Redacted>, and butter sauce.
Don't boil me, I'm still alive.
<Redacted> lobster!
^ permalink raw reply [nested|flat] 3+ messages in thread
end of thread, other threads:[~2025-08-26 18:56 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2025-08-26 17:44 using pgbackrest in a PG streaming replication cfg with repmgr Ghiurea, Isabella <[email protected]>
2025-08-26 18:50 ` Re: using pgbackrest in a PG streaming replication cfg with repmgr Ron Johnson <[email protected]>
2025-08-26 18:56 ` Re: using pgbackrest in a PG streaming replication cfg with repmgr Ron Johnson <[email protected]>
This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox