Re: pgsql: Add pg_audit, an auditing extension

From: Stephen Frost <sfrost(at)snowman(dot)net>
To: Thom Brown <thom(at)linux(dot)com>
Cc: Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, "pgsql-committers(at)postgresql(dot)org" <pgsql-committers(at)postgresql(dot)org>
Subject: Re: pgsql: Add pg_audit, an auditing extension
Date: 2015-05-15 11:10:20
Message-ID: 20150515111020.GT30322@tamriel.snowman.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers pgsql-hackers

* Thom Brown (thom(at)linux(dot)com) wrote:
> If it were empty, it would then be indistinguishable from a statement
> executed with a single parameter passed as an empty string.

NULL, but yes.

> Speaking of which, I notice that nulls show up as nothing too. How
> does one distinguish between an empty string and a null in the logs?

It should be "", to match how the COPY protocol handles it. Will take a
look.

Thanks!

Stephen

In response to

Browse pgsql-committers by date

  From Date Subject
Next Message Fujii Masao 2015-05-15 11:11:22 pgsql: Support VERBOSE option in REINDEX command.
Previous Message Pavel Stehule 2015-05-15 11:04:10 Re: pgsql: Add pg_audit, an auditing extension

Browse pgsql-hackers by date

  From Date Subject
Next Message Arjen Nienhuis 2015-05-15 11:13:33 Re: Patch for bug #12845 (GB18030 encoding)
Previous Message Pavel Stehule 2015-05-15 11:04:10 Re: pgsql: Add pg_audit, an auditing extension