Thank you. I was thinking along the same lines, but I am not sure I
understand why the setup will fall apart on failover. If I also have
archive_mode always on the primary site, I think that I just need to
pg_rewind (or PITR restore) old primary and configure it as a secondary to
the new master fol
What you are asking for is tricky, but possible. You can setup two repos,
one for each server. On the first server (in datacenter A), you have a
"normal" pgbackrest configuration, with an explicit backup-standby=n. pg1-*
points to the local server, pg2-* points to the replica. The repo is in
datace
Wow, 9 days is a long time. The fact that it is not responding to
pg_terminate_backend means it's not even calling CHECK_FOR_INTERRUPTS
inside the WaitForParallelWorkersToFinish loop, so something is seriously
wrong. If the PID is still there, please do what Laurenz suggested:
strace -tp 356274
I
Hello,
Is it possible to configure pgbackrest for a postgresql server pair using
physical replication on two different sites with limited bandwidth (i.e.
sufficient for data replication but not daily backups)? All tutorials and
blogs describe a setup with either a single pgbackrest repo or multipl
pgsql 17.5 on Red Hat Enterprise Linux release 8.10 (Ootpa)
The query is run from one of our php applications.
On Fri, Nov 7, 2025 at 8:59 PM Laurenz Albe
wrote:
> On Fri, 2025-11-07 at 19:18 +0530, Ashish Mukherjee wrote:
> > I have a query like this showing up on my production database -
> >
