Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > comp.databases.postgresql > #843

Re: archiver problem

Show all headers | View raw

mandag 1. oktober 2018 18.19.52 UTC+2 skrev Laurenz Albe følgende:
> 
> You must have removed that WAL file from "pg_xlog" before it was archived.
> 
> To get rid of this error, you can temporarily set
> 
>    archive_command = '/bin/true'
> 
> Then PostgreSQL will believe that the WAL files are archived correctly,
> even though they are not.
> 
> Once pg_stat_archiver shows that PostgreSQL has caught up to WAL files
> that actually exist, you can restore the original setting.
> 
> After that, create a new base backup as soon as possible!

Hi, thanks a lot for this answer. I would have helped me just like I wanted.

And. Yes, you are correct. My disk filled up 100% due to an archiving problem and I was stupid enough to run the pg_archivecleanup command. I later understod that this only should be used on the replica node.

I tried to stop the archiving and start it againg, but it did not help. So in the end I ended up stopping the master, promoting my replica node and change the WAL streaming direction.

Next time (hope there will be no next time) I will set the archive_command to '/bin/true' instead, that is a great solution. Thanks a lot Laurenz!!

Kind regards, Alf

Back to comp.databases.postgresql | Previous | Next — Previous in thread | Find similar

Thread

archiver problem Alf Normann Klausen <alf@svada.com> - 2018-09-27 13:36 -0700
  Re: archiver problem Laurenz Albe <laurenz@nospam.pn> - 2018-10-01 16:19 +0000
    Re: archiver problem Alf Normann Klausen <alf@svada.com> - 2018-10-02 03:59 -0700

csiph-web