| commit | e943cff33d6bc6db3011a243d9b7ccd1a0472e62 | |
| author | Tom Lane <tgl@sss.pgh.pa.us> | |
| Mon, 9 Oct 2023 15:29:21 +0000 (9 11:29 -0400) | ||
| committer | Tom Lane <tgl@sss.pgh.pa.us> | |
| Mon, 9 Oct 2023 15:29:36 +0000 (9 11:29 -0400) | ||
| tree | 7153d5f2e43d6c271966a62503160224a7f2f821 | treesnapshot (tar.gz zip) |
| parent | 9154ededfc99e7637cd61b4ca10f28796125ece2 | commitdiff |
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
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 | diffblobblamehistory |