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:21 +0000 (11:29 -0400)
commit64aad6944c8d331ceb6a0b2df73bf70c5adaf35b
treee1a1efbaf879f2e72351d3b8250f400bfa690ef2
parent637109d13ab2684aa7ad4e893137e7487b5e8490
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