On Thu, Jul 11, 2013 at 1:03 AM, Daniel Farina wrote:
> I had a report from a user asking how they could VACUUM in the future
> under 9.3, when it's no longer supported (which took me aback). He
> referred me to a manual page:
>
> http://www.postgresql.org/docs/current/static/sql-vacuum.html
>
>
On 7/12/13 6:28 AM, Magnus Hagander wrote:
> "This page in other versions: 9.2 / 9.1 / 9.0 / 8.4 | Unsupported
>> versions: 9.3 / 8.3 / 8.2 / 8.1 / 8.0 / 7.4 / 7.3 / 7.2 / 7.1 / devel"
"This page in other versions: 9.2 / 9.1 / 9.0 / 8.4 | Devel: 9.3 |
EOL: 8.3 / 8.2 / 8.1 / 8.0 / 7.4 / 7.3 / 7
On Fri, Jul 12, 2013 at 3:28 AM, Magnus Hagander wrote:
>
> On Thu, Jul 11, 2013 at 1:03 AM, Daniel Farina wrote:
> > I had a report from a user asking how they could VACUUM in the future
> > under 9.3, when it's no longer supported (which took me aback). He
> > referred me to a manual page:
> >
Daniel Farina writes:
> On Fri, Jul 12, 2013 at 3:28 AM, Magnus Hagander wrote:
>> But I can understand the confusion - do you have a suggestion for how
>> to write it to make it more obvious what the actual problem is?
> I don't think I communicated the problem right.
Yeah, you did, but we nee
-BEGIN PGP SIGNED MESSAGE-
Hash: RIPEMD160
> "This page in other versions: 9.2 / 9.1 / 9.0 / 8.4 | Unsupported
> versions: 9.3 / 8.3 / 8.2 / 8.1 / 8.0 / 7.4 / 7.3 / 7.2 / 7.1 / devel"
>
> An entirely reasonable person would decide that the VACUUM command is
> unsupported in any of the
On Fri, Jul 12, 2013 at 9:01 PM, Greg Sabino Mullane wrote:
>
>
> How about we simply list all versions, without classifying them as
> unsupported or not?
>
Is there an automated mechanism by which a version would move from the
'supported' group to the 'unsupported' group, eg, when 8.4 goes EOL?
