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

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>
Cc: 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:27:58
Message-ID: 5877.1576524478@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-docs

Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> writes:
> po 16. 12. 2019 v 12:12 odesílatel PG Doc comments form <
> noreply(at)postgresql(dot)org> napsal:
>> I'm wondering if it would be worthwhile to put a totally generic auditing
>> function into the documentation e.g.
>> [ snip ]

> Just few points to this code

I agree this code could have better style, but maybe that is just more
evidence that a well-written example would be helpful?

regards, tom lane

In response to

Responses

Browse pgsql-docs by date

  From Date Subject
Next Message Daniel Gustafsson 2019-12-16 19:35:22 Re: Example 42.4. A PL/pgSQL Trigger Function for Auditing
Previous Message Pavel Stehule 2019-12-16 11:25:34 Re: Example 42.4. A PL/pgSQL Trigger Function for Auditing