Re: Update documentation for SET to include SCHEMA / NAMES syntax

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Álvaro Rodríguez <alvarorodriguez(dot)garcia(at)datadoghq(dot)com>
Cc: pgsql-hackers(at)lists(dot)postgresql(dot)org
Subject: Re: Update documentation for SET to include SCHEMA / NAMES syntax
Date: 2026-03-27 17:53:11
Message-ID: 1339792.1774633991@sss.pgh.pa.us
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

=?UTF-8?B?w4FsdmFybyBSb2Ryw61ndWV6?= <alvarorodriguez(dot)garcia(at)datadoghq(dot)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

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message shihao zhong 2026-03-27 18:05:22 Re: [Patch] New pg_stat_tablespace view
Previous Message Andres Freund 2026-03-27 17:29:03 Re: Don't synchronously wait for already-in-progress IO in read stream