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

Peripheral Links

Header And Logo

PostgreSQL
| The world's most advanced open source database.

Site Navigation

Search archives
  Advanced Search

Re: Inheritance mention


  • From: Scott Marlowe <scott(dot)marlowe(at)gmail(dot)com>
  • To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
  • Cc: Euler Taveira de Oliveira <euler(at)timbira(dot)com>, Bruce Momjian <bruce(at)momjian(dot)us>, PostgreSQL-documentation <pgsql-docs(at)postgresql(dot)org>
  • Subject: Re: Inheritance mention
  • Date: Mon, 13 Apr 2009 10:47:32 -0600
  • Message-id: <dcc563d10904130947v39309a9ahab513bad19388dd3@mail.gmail.com> <text/plain>

On Mon, Apr 13, 2009 at 12:04 AM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Euler Taveira de Oliveira <euler(at)timbira(dot)com> writes:
>> Bruce Momjian escreveu:
>>> Do people feel we should continue documenting that Postgres pre-7.1
>>> didn't reference child tables by default?
>>>
>> No. IMHO we should remove references to unsupported releases from documentation.
>
> "Unsupported releases" is far too strict a criterion for this.  For
> example, there are demonstrably still people using 7.2 (we had a
> question about it just last week).  They will still appreciate these
> notes when they get around to updating.
>
> Pre-7.1 might indeed be old enough to cut, but how much are we really
> saving?  Four sentences out of our current docs doesn't excite me ...

But since there's a doc set per version, it would make sense to stop
mentioning unsupported versions in the docs for supported versions,
no?  Or is this a FAQ thing we're talking about?



Home | Main Index | Thread Index

Privacy Policy | About PostgreSQL
Copyright © 1996 – 2012 PostgreSQL Global Development Group