Re: Typo in PL/pgSQL trigger Example 43.4?

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Daniel Gustafsson <daniel(at)yesql(dot)se>
Cc: "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>, 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-09 13:45:46
Message-ID: 133678.1696859146@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-docs

Daniel Gustafsson <daniel(at)yesql(dot)se> writes:
>> On 7 Oct 2023, at 22:22, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>> 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.

> Agreed, and "user" is a hard search term to use for discovering what it is. +1
> for changing to current_user.

OK, I'll take care of this later today.

regards, tom lane

In response to

Browse pgsql-docs by date

  From Date Subject
Next Message Brad White 2023-10-09 17:34:26 Re: ODBC options
Previous Message Tim Needham 2023-10-09 10:38:43 Re: Example numeric constants aren't valid?