Oct 2023

1 commit
Doc: use CURRENT_USER not USER in plpgsql trigger examples.
9 Oct 2023Tom Lanemaster17beta1REL_19_STABLE17beta1REL_18_STABLE17beta1REL_17_STABLE17beta1REL_16_STABLE16.1REL_15_STABLE15.5REL_14_STABLE14.10REL_13_STABLE13.13+2 more
LLM analysis, 100% surewritten from the discussion, no matching patch2 of 2 reviewers saw the final version

Kirk Parker questioned the unexplained use of user in #3, and Tom Lane proposed current_user for clarity in #5 and undertook the change in #8. The commit implements that agreed approach with nine substitutions across three trigger examples in doc/src/sgml/plpgsql.sgml; no patch was attached.

  • Kirk Parkersaw the final versionLLM analysis, 97% sureKirk endorsed the proposed change before the commit and pointed out that the preceding example already used current_user in #6.
  • Daniel Gustafssonsaw the final versionLLM analysis, 100% sureDaniel explicitly endorsed current_user before the commit because user is difficult to search for in #7.

Credits across 1 commit

Committer
Tom Lane1