Skip site navigation (1) Skip section navigation (2)

Re: Re: [COMMITTERS] pgsql: Make standby server continuously retry restoring the next WAL

From: Dimitri Fontaine <dfontaine(at)hi-media(dot)com>
To: Simon Riggs <simon(at)2ndQuadrant(dot)com>
Cc: Fujii Masao <masao(dot)fujii(at)gmail(dot)com>, Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Re: [COMMITTERS] pgsql: Make standby server continuously retry restoring the next WAL
Date: 2010-02-12 17:25:02
Message-ID: m2ljeywemp.fsf@hi-media.com (view raw or flat)
Thread:
Lists: pgsql-committerspgsql-docspgsql-hackers
Simon Riggs <simon(at)2ndQuadrant(dot)com> writes:
> Attached patch implements pg_standby for use as an
> archive_cleanup_command, reusing existing code with new -a option.
>
> Happy to add the archive_cleanup_command into main server as well, if
> you like. Won't take long.

Would it be possible to have the server do the cleanup (and the cp for
that matter) on its own or use a script?

Either have archive_cleanup = on and either an commented out (empty)
archive_cleanup_command and the same for the restore_command, or a
special magic value, like 'postgresql' to activate the internal one.

This way we have both a zero config working default setup and the
flexibility to adapt to any archiving solution our user might already be
using.

A default archive_command would be nice too. Like you give it a
directory name or a rsync path and it does the basic right thing.

I'm not sure my detailed approach is the right one, but the birdview is
to have the simple case really simple to setup, and the complex cases
still possible. Default included archive, restore and cleanup commands
would be awesome.

Oh, and the basic simple case actually is with a remote standby. Without
NFS or the like, no shared mount point for archiving. 

Regards,
-- 
dim

In response to

Responses

pgsql-docs by date

Next:From: Greg StarkDate: 2010-02-12 17:47:49
Subject: Re: [COMMITTERS] pgsql: Make standby server continuously retry restoring the next WAL
Previous:From: Thom BrownDate: 2010-02-12 16:15:03
Subject: Re: Confusing link in streaming replication section

pgsql-hackers by date

Next:From: Robert HaasDate: 2010-02-12 17:34:21
Subject: Re: [PATCH] Provide rowcount for utility SELECTs
Previous:From: Euler Taveira de OliveiraDate: 2010-02-12 17:13:06
Subject: Re: TCP keepalive support for libpq

pgsql-committers by date

Next:From: Tom LaneDate: 2010-02-12 17:33:21
Subject: pgsql: Extend the set of frame options supported for window functions.
Previous:From: Heikki LinnakangasDate: 2010-02-12 16:10:05
Subject: Re: Re: [COMMITTERS] pgsql: Make standby server continuously retry restoring the next WAL

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group