Re: archive falling behind

From: Strahinja Kustudić <strahinjak(at)nordeus(dot)com>
To: German Becker <german(dot)becker(at)gmail(dot)com>
Cc: "pgsql-admin(at)postgresql(dot)org" <pgsql-admin(at)postgresql(dot)org>
Subject: Re: archive falling behind
Date: 2013-04-25 22:45:49
Message-ID: CADKbJJXc7yTf7VLzDpvwE+up6gXjyM2WaDFevBhELpAptxoXVQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-admin

How can the archive process fall behind? Postgres will never reuse WAL
files which are not yet archived.

Regarding your question about slowing down WAL generation, that is not
possible to do, unless you slow down the application which is doing the
writing into the database.

Regards,
Strahinja

On Mon, Apr 22, 2013 at 6:03 PM, German Becker <german(dot)becker(at)gmail(dot)com>wrote:

> Hi I am working with version 9.1.9. The dabase is in archiving mode. The
> archives are then sended to a hotstandby replication sever.
> I have seen that under heavy load, the archive process will fall behind
> the WAL generation and thuse some WAL segments won't get archived so the
> replication stops. To recover from this I need to do a new cold backup and
> send it to the replication server. Is there a way to limit the WAL
> generation (i.e slowing down insterts and deletes) so as to prevent the
> archive from falling behind?
>
> Thanks!!
>

In response to

Responses

Browse pgsql-admin by date

  From Date Subject
Next Message Rodrigo Barboza 2013-04-26 03:53:38 Size of pgstat.stat
Previous Message Tom Lane 2013-04-25 19:54:55 Re: [ADMIN] Simultaneous index creates on different schemas cause deadlock?