Re: Update documentation for SET to include SCHEMA / NAMES syntax - Mailing list pgsql-hackers

From Tom Lane
Subject Re: Update documentation for SET to include SCHEMA / NAMES syntax
Date
Msg-id 1339792.1774633991@sss.pgh.pa.us
Whole thread Raw
In response to Update documentation for SET to include SCHEMA / NAMES syntax  (Álvaro Rodríguez <alvarorodriguez.garcia@datadoghq.com>)
List pgsql-hackers
=?UTF-8?B?w4FsdmFybyBSb2Ryw61ndWV6?= <alvarorodriguez.garcia@datadoghq.com> writes:
> The attached patch updates the documentation for the SET statement to
> include the special syntax for SCHEMA / NAMES in the synopsis. The
> current documentation only mentions this special syntax under the
> parameters, which is confusing and different from the usual practice.

Hmm.  It's true that SET SCHEMA / SET NAMES are in the SQL standard,
but I think they are semi-deprecated for Postgres despite that.
They are confusing because they are aliases for GUC parameters that
are named significantly differently from the standard's syntax,
so I doubt we want to encourage their use.  That being the case,
I'm content to leave them buried in the Parameters section.

SET TIME ZONE is also a SQL-standard thing, but it's more acceptable
because the syntax is sufficiently closely related to the GUC's name.

            regards, tom lane



pgsql-hackers by date:

Previous
From: Andres Freund
Date:
Subject: Re: Don't synchronously wait for already-in-progress IO in read stream
Next
From: shihao zhong
Date:
Subject: Re: [Patch] New pg_stat_tablespace view