| From: | Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| 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:42:04 |
| Message-ID: | CAFj8pRDAmZAdM_-4skPt0NZ=YR3S3PD1Bm_Q=OnjjQYSX9Vj3Q@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-docs |
Dne po 16. 12. 2019 20:28 uživatel Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> napsal:
> 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?
>
+1
there is not too much examples for trigger parameters.
> regards, tom lane
>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Dave Cramer | 2019-12-17 11:42:53 | client auth docs seem to have devolved |
| Previous Message | Daniel Gustafsson | 2019-12-16 19:35:22 | Re: Example 42.4. A PL/pgSQL Trigger Function for Auditing |