Re: Example 42.4. A PL/pgSQL Trigger Function for Auditing

From: Daniel Gustafsson <daniel(at)yesql(dot)se>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>, simon(dot)dallaway(at)datacom(dot)co(dot)nz, pgsql-docs(at)lists(dot)postgresql(dot)org
Subject: Re: Example 42.4. A PL/pgSQL Trigger Function for Auditing
Date: 2019-12-16 19:35:22
Message-ID: 45AB23EB-B6D5-46A2-B2B2-8E03138FCA85@yesql.se
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-docs

> On 16 Dec 2019, at 20:27, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>
> .. maybe that is just more
> evidence that a well-written example would be helpful?

I think thats the key takeaway here. +1 on the gist of the suggestion that
started this thread.

cheers ./daniel

In response to

Browse pgsql-docs by date

  From Date Subject
Next Message Pavel Stehule 2019-12-16 19:42:04 Re: Example 42.4. A PL/pgSQL Trigger Function for Auditing
Previous Message Tom Lane 2019-12-16 19:27:58 Re: Example 42.4. A PL/pgSQL Trigger Function for Auditing