From: | Arthur Zakirov <a(dot)zakirov(at)postgrespro(dot)ru> |
---|---|
To: | Luca Ferrari <fluca1978(at)gmail(dot)com>, pgsql-general <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: pgaudit.log_parameter |
Date: | 2019-07-31 12:58:15 |
Message-ID: | 824ca351-a4ff-6bb1-a534-9435e4f9a7a9@postgrespro.ru |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Hello,
On 31.07.2019 14:21, Luca Ferrari wrote:
> Hello,
> I'm a little confused about the setting pgaudit.log_parameter of the
> pgaudit extension
> (https://github.com/pgaudit/pgaudit/blob/master/README.md)
> What's the purpose of this? AN example of query that will trigger such
> parameter logging? Apparently I cannot get it providing me more
> information than '<none>'.
pgaudit.log_parameter allows to log parameters of prepared statements.
See the documentation:
https://www.postgresql.org/docs/current/sql-prepare.html
The following example logs parameters if pgaudit.log_parameter is on:
EXECUTE fooplan(1, 'Hunter Valley', 't', 200.00);
It should log parameters: 1, 'Hunter Valley', 't', 200.00
--
Arthur Zakirov
Postgres Professional: http://www.postgrespro.com
Russian Postgres Company
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2019-07-31 14:03:13 | Re: Active connections are terminated because of small wal_sender_timeout |
Previous Message | Artur Zakirov | 2019-07-31 12:57:34 | Re: pgaudit.log_parameter |