projects / postgresql.git / commit
? search:
summary | shortlog | log | commit | commitdiff | tree
(parent: a0b0136) | patch
Doc: use CURRENT_USER not USER in plpgsql trigger examples.
authorTom Lane <tgl@sss.pgh.pa.us>
Mon, 9 Oct 2023 15:29:21 +0000 (11:29 -0400)
committerTom Lane <tgl@sss.pgh.pa.us>
Mon, 9 Oct 2023 15:30:07 +0000 (11:30 -0400)
commitb36d78e21a848761af4d7f360425819b1b40067d
tree5eb0b2b53b8a19f504c26c04e2856a238671e396tree
parenta0b0136259080c0441f4ff1c7d65d8a9d08360cfcommit | diff
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
doc/src/sgml/plpgsql.sgml diff | blob | blame | history
This is the main PostgreSQL git repository.