Received: from localhost (unknown [200.46.204.183])
	by mail.postgresql.org (Postfix) with ESMTP id 270EC65019F
	for <pgsql-docs-postgresql.org@mail.postgresql.org>;
	Thu, 27 Nov 2008 14:56:18 -0400 (AST)
Received: from mail.postgresql.org ([200.46.204.86])
	by localhost (mx1.hub.org [200.46.204.183]) (amavisd-maia, port 10024)
	with ESMTP id 37196-04 for
	<pgsql-docs-postgresql.org@mail.postgresql.org>;
	Thu, 27 Nov 2008 14:56:15 -0400 (AST)
X-Greylist: domain auto-whitelisted by SQLgrey-1.7.6
Received: from smtp3.clear.net.nz (smtp3.clear.net.nz [203.97.33.64])
	by mail.postgresql.org (Postfix) with ESMTP id 131556501A5
	for <pgsql-docs@postgresql.org>; Thu, 27 Nov 2008 14:56:14 -0400 (AST)
Received: from zmori.markir.net
	(121-73-168-7.dsl.telstraclear.net [121.73.168.7])
	by smtp3.clear.net.nz (CLEAR Net Mail)
	with ESMTP id <0KB000J8P9XME810@smtp3.clear.net.nz> for
	pgsql-docs@postgresql.org; Fri, 28 Nov 2008 07:56:11 +1300 (NZDT)
Date: Fri, 28 Nov 2008 07:56:09 +1300
From: Mark Kirkwood <markir@paradise.net.nz>
Subject: Re: pg_standby supported versions
In-reply-to: <1227805902.20796.69.camel@hp_dx2400_1>
To: Simon Riggs <simon@2ndQuadrant.com>
Cc: Decibel! <decibel@decibel.org>, pgsql-docs@postgresql.org
Message-id: <492EED49.6060707@paradise.net.nz>
MIME-version: 1.0
Content-type: text/plain; charset=ISO-8859-1; format=flowed
Content-transfer-encoding: 7bit
References: <48A2B07E.2060608@paradise.net.nz>
	<A417B4FB-99C0-4863-8CB7-DA0E5B42AD78@decibel.org>
	<1219743030.5343.1265.camel@ebony.2ndQuadrant>
	<492D1392.2020004@paradise.net.nz>
	<1227805902.20796.69.camel@hp_dx2400_1>
User-Agent: Thunderbird 2.0.0.17 (X11/20081109)
X-Virus-Scanned: Maia Mailguard 1.0.1
X-Spam-Status: No, hits=0 tagged_above=0 required=5 tests=none
X-Spam-Level: 
X-Archive-Number: 200811/22
X-Sequence-Number: 5007

Simon Riggs wrote:
> On Wed, 2008-11-26 at 22:14 +1300, Mark Kirkwood wrote:
>   
>>
>> Exactly, after posting this I discovered the relevant CVS logs for 
>> changes to support restartable recovery. It seems to me that perhaps a 
>> little more detail in the docs would be good here.
>>     
>
> I would hope that the complete absence of anything would be all that is
> required to dissuade people. We don't ever update the docs to say "BTW
> feature X is not supported until next release". Not sure we should start
> now.
>
>   

While I understand, I also think it is perfectly reasonable to clarify 
why a specific minimum version is being recommended. To me this conforms 
to the open source spirit of telling folk why something is true, as 
opposed to stating that it is.

I'm thinking of something like:

<para>

pg_standby is designed to work with PostgreSQL 8.2 and later, as it 
requires the ability to interrupt and restart recovery (absent in 
earlier server versions).

</para>