| From: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
|---|---|
| To: | Silvio Fabi - NBS srl <s(dot)fabi(at)nbsgroup(dot)it> |
| Cc: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: postgres: archiver process failed on 000000010000020A00000073 |
| Date: | 2020-04-01 17:36:06 |
| Message-ID: | 20200401173606.GA24159@alvherre.pgsql |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On 2020-Apr-01, Silvio Fabi - NBS srl wrote:
> WAL Archive process on my DB Postgresql 10 is not working.
> the WAL Archive file 000000010000020A00000073 was accidentally deleted
> and there is no backup.
> Postgresql tries to run the following command:
> rsync -a pg_wal/000000010000020A00000073
> barman(at)database:/var/lib/barman/database/incoming/000000010000020A00000073
Ouch. This is not a barman problem; accidentally a WAL file is
synonymous with corrupting your database. Any existing backup that
needs that file is now invalid. I suggest you run CHECKPOINT and then
take a new backup. I think removing the 000000010000020A00000073.ready
file from pg_wal should prevent future attempts at archiving it, so that
subsequent WAL files are archived.
By all means, *do not* lose any more WAL files. It is a very dangerous
thing to do.
--
Álvaro Herrera https://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | negora | 2020-04-01 19:44:44 | Re: dbeaver |
| Previous Message | Silvio Fabi - NBS srl | 2020-04-01 17:09:59 | postgres: archiver process failed on 000000010000020A00000073 |