| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | pgsql-committers(at)lists(dot)postgresql(dot)org |
| Subject: | pgsql: Doc: use CURRENT_USER not USER in plpgsql trigger examples. |
| Date: | 2023-10-09 15:31:10 |
| Message-ID: | E1qpsDt-000oFc-Tb@gemulon.postgresql.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | 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_16_STABLE
Details
-------
https://git.postgresql.org/pg/commitdiff/e943cff33d6bc6db3011a243d9b7ccd1a0472e62
Modified Files
--------------
doc/src/sgml/plpgsql.sgml | 18 +++++++++---------
1 file changed, 9 insertions(+), 9 deletions(-)
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Michael Paquier | 2023-10-10 00:07:08 | pgsql: worker_spi: Fix another stability issue with BGWORKER_BYPASS_ALL |
| Previous Message | Heikki Linnakangas | 2023-10-09 08:52:41 | pgsql: Rename StartBackgroundWorker() to BackgroundWorkerMain(). |