On 8/12/25 22:48, px shi wrote:
Here’s a scenario: The latest WAL file on the primary node is
000100AF, and the standby node has also received up to
000100AF. However, the latest WAL file that has been
successfully archived from the primary is only 000100
>
>
> Justin 于2025年8月13日周三 10:51写道：
>
>>
>>
>> On Tue, Aug 12, 2025 at 10:24 PM px shi wrote:
>>
>>> How often does your primary node crash, and then not recover due to WALs
corruption or WALs not existing?
If it's _ever_ happened, you should _fix that_ instead of rolling your
I think you missed this rather critical bit on the Github, Daniel
"Post-August 28th, 2025
- For development purposes, community-tier users are restricted to pulling only
the most recent ‘latest’ tags of the limited community-tier subset of container
images.
- Production users should subscri
On Wed, Aug 13, 2025 at 2:49 PM Ruben Morais
wrote:
> Hi,
>
> Simply update the postgres.conf with the desired stanza, and add the new
> one in the pgbackrest.conf file.
> After that, run stanza-create with the new name.
> Once everything is OK, go to the repository directory and remove all files
Hi,
Simply update the postgres.conf with the desired stanza, and add the new
one in the pgbackrest.conf file.
After that, run stanza-create with the new name.
Once everything is OK, go to the repository directory and remove all files
related to that stanza.
With this approach, there’s no downtime
On Wed, Aug 13, 2025 at 1:24 PM Ruben Morais
wrote:
> Hi,
>
> All seems ok, but in your check command you use a different stanza name
> from the configuration and from what you have in postgres.log file.
>
> Created stanza successfully :on my Repo server
> [root@db01 ~]# sudo -u pgbackrest p
Hi,
All seems ok, but in your check command you use a different stanza name
from the configuration and from what you have in postgres.log file.
Created stanza successfully :on my Repo server
[root@db01 ~]# sudo -u pgbackrest pgbackrest --stanza=K_Repo
--log-level-console=info stanza-create
s
Hi all,
I have configured pgbackrest on ( RHEL 9.3 , pgbackrest 2.52.1 database
version 16 ) for a remote repo machine (RHEL 9.3, pgbackrest 2.52.1 )
I have created the stanza K_repo
archive_command = 'pgbackrest --stanza=K_Repo archive-push %p'in
postgresql.conf
Created stanza succ
