pgsql: Doc: use CURRENT_USER not USER in plpgsql trigger examples. - Mailing list pgsql-committers

From Tom Lane
Subject pgsql: Doc: use CURRENT_USER not USER in plpgsql trigger examples.
Date
Msg-id E1qpsDt-000oFh-Uc@gemulon.postgresql.org
Whole thread Raw
List pgsql-committers
Doc: use CURRENT_USER not USER in plpgsql trigger examples.

While these two built-in functions do exactly the same thing,
CURRENT_USER seems preferable to use in documentation examples.
It's easier to look up if the reader is unsure what it is.
Also, this puts these examples in sync with an adjacent example
that already used CURRENT_USER.

Per question from Kirk Parker.

Discussion: https://postgr.es/m/CANwZ8rmN_Eb0h0hoMRS8Feftaik0z89PxVsKg+cP+PctuOq=Qg@mail.gmail.com

Branch
------
REL_14_STABLE

Details
-------
https://git.postgresql.org/pg/commitdiff/9f597bafac20d78db713904f97425e2994e6d6b0

Modified Files
--------------
doc/src/sgml/plpgsql.sgml | 18 +++++++++---------
1 file changed, 9 insertions(+), 9 deletions(-)


pgsql-committers by date:

Previous
From: Heikki Linnakangas
Date:
Subject: pgsql: Clarify the checks in RegisterBackgroundWorker.
Next
From: Michael Paquier
Date:
Subject: pgsql: worker_spi: Fix another stability issue with BGWORKER_BYPASS_ALL