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

Re: [HACKERS] Docs for archive_cleanup_command are poor

From: Brendan Jurd <direvus(at)gmail(dot)com>
To: Simon Riggs <simon(at)2ndquadrant(dot)com>
Cc: Fujii Masao <masao(dot)fujii(at)gmail(dot)com>, Robert Haas <robertmhaas(at)gmail(dot)com>, pgsql-hackers(at)postgresql(dot)org, pgsql-docs(at)postgresql(dot)org
Subject: Re: [HACKERS] Docs for archive_cleanup_command are poor
Date: 2010-10-14 18:51:28
Message-ID: AANLkTimiQrsWrc3eyiP91QnxPDwEqx=X7wwRuFxKC8rF@mail.gmail.com (view raw or flat)
Thread:
Lists: pgsql-docspgsql-hackers
On 15 October 2010 05:33, Simon Riggs <simon(at)2ndquadrant(dot)com> wrote:
> On Fri, 2010-10-15 at 02:24 +1100, Brendan Jurd wrote:
>> I'll drop this onto the next open commitfest.  If it passes muster, it
>> sure wouldn't hurt to backpatch it to 9.0.
>
> Committed. Not sure there's anything there worth backpatching? There
> aren't any doc bugs there.
>

Thanks for the commit Simon.

Agreed that there are no doc bugs.  The reason I suggested a backpatch
is that I'm concerned that a lot of people are going to be approaching
the whole Standby topic for the first time with 9.0, so it would be
nice to give those folks an accessible account of how
archive_cleanup_command is meant to be used.

I was also working from the assumption that the "we only packpatch bug
fixes" policy applied to the code, not so much to the documentation.
If I was in error about that, well fair enough then.

Cheers,
BJ

In response to

Responses

pgsql-docs by date

Next:From: Robert HaasDate: 2010-10-14 19:09:45
Subject: Re: Documenting removal of nonnullvalue() and friends
Previous:From: Robert HaasDate: 2010-10-14 18:50:26
Subject: Re: [HACKERS] Docs for archive_cleanup_command are poor

pgsql-hackers by date

Next:From: Dmitriy IgrishinDate: 2010-10-14 18:59:00
Subject: How to determine failed connection attempt due to invalid authorization (libpq)?
Previous:From: Robert HaasDate: 2010-10-14 18:50:26
Subject: Re: [HACKERS] Docs for archive_cleanup_command are poor

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