projects / postgresql.git / commit
? search:
summary | shortlog | log | commit | commitdiff | tree
(parent: 9154ede) | 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:29:36 +0000 (11:29 -0400)
commite943cff33d6bc6db3011a243d9b7ccd1a0472e62
tree7153d5f2e43d6c271966a62503160224a7f2f821tree
parent9154ededfc99e7637cd61b4ca10f28796125ece2commit | 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.