projects / postgresql.git / commit
? search:
summary | shortlog | log | commit | commitdiff | tree
(parent: 4f16152) | 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:35 +0000 (11:30 -0400)
commit694d6700e8866941a72b9f34955fc6ede67cbd63
treed65e348d6e5f4a599e035ddbf6e263a6d6c15977tree
parent4f16152d9711a59e1b2ad8a4bc26d4455da709e6commit | 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: http://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.