From: Tom Lane <tgl@sss.pgh.pa.us>
To: Dave Cramer <davecramer@postgres.rocks>
cc: pgsql-docs@lists.postgresql.org
Subject: Re: documenting divergence from the SQL spec
In-reply-to: 
 <CADK3HHJFqxggENTUdHmrLswDuLgDtHTE+KzXWhC6epZe=ymhuQ@mail.gmail.com>
References: 
 <CADK3HHJFqxggENTUdHmrLswDuLgDtHTE+KzXWhC6epZe=ymhuQ@mail.gmail.com>
Comments: In-reply-to Dave Cramer <davecramer@postgres.rocks>
	message dated "Fri, 14 Feb 2020 11:05:25 -0500"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <12152.1581697573.1@sss.pgh.pa.us>
Content-Transfer-Encoding: quoted-printable
Date: Fri, 14 Feb 2020 11:26:13 -0500
Message-ID: <12153.1581697573@sss.pgh.pa.us>
Precedence: bulk

Dave Cramer <davecramer@postgres.rocks> writes:
> We have a section in the main docs for conformance
> https://www.postgresql.org/docs/12/features.html
> And then this https://wiki.postgresql.org/wiki/PostgreSQL_vs_SQL_Standar=
d for
> divergence.
> I'd like to see the divergence section put into the main docs so that it=
 is
> easier to find.

The individual statement reference pages already have sections for
standards divergences.  Admittedly, that framework doesn't help for
discrepancies that can't be tied to a statement type ... but I don't
think we should throw in duplicative material of this sort.  It's
tough enough to keep one instance of the info up-to-date.  So I'd
want to see some structure for this that respects that existing
set of information.

			regards, tom lane