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

Re: Command to prune archive at restartpoints

From: Simon Riggs <simon(at)2ndQuadrant(dot)com>
To: Andrew Dunstan <andrew(at)dunslane(dot)net>
Cc: Robert Haas <robertmhaas(at)gmail(dot)com>, Greg Stark <gsstark(at)mit(dot)edu>, Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Command to prune archive at restartpoints
Date: 2010-06-09 07:21:08
Message-ID: 1276068068.12489.6512.camel@ebony (view raw or flat)
Thread:
Lists: pgsql-hackers
On Tue, 2010-06-08 at 18:30 -0400, Andrew Dunstan wrote:

> I prefer archive_cleanup_command. We should name things after their 
> principal function, not an implementation detail, IMNSHO.
> 
> More importantly, we should include an example in the docs. I created 
> one the other day  when this was actually bothering me a bit (see 
> <http://people.planetpostgresql.org/andrew/index.php?/archives/85-Keeping-a-hot-standby-log-archive-clean.html>). 
> That seemed to work ok, but maybe it's too long, and maybe people would 
> prefer a shell script to perl.

I submitted a patch to make the command "pg_standby -a %r"

That's a more portable solution, ISTM.

I'll commit that and fix the docs.

-- 
 Simon Riggs           www.2ndQuadrant.com


In response to

Responses

pgsql-hackers by date

Next:From: Dean RasheedDate: 2010-06-09 07:51:41
Subject: Re: Invalid YAML output from EXPLAIN
Previous:From: Simon RiggsDate: 2010-06-09 07:19:29
Subject: Re: Command to prune archive at restartpoints

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