From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
Cc: | Kirk Parker <khp(at)equatoria(dot)us>, pgsql-docs(at)lists(dot)postgresql(dot)org |
Subject: | Re: Typo in PL/pgSQL trigger Example 43.4? |
Date: | 2023-10-07 20:22:01 |
Message-ID: | 3179621.1696710121@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-docs |
"David G. Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> writes:
> On Sat, Oct 7, 2023 at 11:11 AM Kirk Parker <khp(at)equatoria(dot)us> wrote:
>> INSERT INTO emp_audit SELECT 'D', now(), user, OLD.*; -- <= ARGUMENT IN QUESTION
>> The emp_audit table has a column named 'userid', which in actual usage
>> (next-to-last line quoted) is populated by 'user' which seems undefined in
>> the context. Was that intended to be 'current_user', or am I missing
>> something?
> user is a valid pseudo-function:
> https://www.postgresql.org/docs/current/functions-info.html#FUNCTIONS-INFO-SESSION
Yeah, either way has the same result. However, I wonder if we should
change this example to use current_user for clarity. It does look
more like it's intended to be a variable or column reference than
a built-in function.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Kirk Parker | 2023-10-09 04:36:36 | Re: Typo in PL/pgSQL trigger Example 43.4? |
Previous Message | David G. Johnston | 2023-10-07 18:15:34 | Re: Typo in PL/pgSQL trigger Example 43.4? |