| From: | oleg yusim <olegyusim(at)gmail(dot)com> |
|---|---|
| To: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
| Cc: | Jerry Sievers <gsievers19(at)comcast(dot)net>, Scott Mead <scottm(at)openscg(dot)com>, John R Pierce <pierce(at)hogranch(dot)com>, PostgreSQL General <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: Loggingt psql meta-commands |
| Date: | 2015-12-10 20:56:01 |
| Message-ID: | CAKd4e_G0yAwz59qTsiSU5VQe6EoJintffUSYrkJodLfs5pzwKQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
So what I want to accomplish is logging queries for roles/privileges with
minimal increasing volume of logs along the way. The idea I got from
responses in this thread so far is:
1) Set log_statement on postgresql.conf to 'mod'
2) Raise log_statement to 'all' but only for postgres superuser
What seems to be open questions to me with this model:
1) Way to check what log_statement set to on per user basis (what table
should I query?)
2) Way to ensure that only superuser can run meta commands, such as \du,
\dp, \z
Thanks,
Oleg
On Thu, Dec 10, 2015 at 2:50 PM, David G. Johnston <
david(dot)g(dot)johnston(at)gmail(dot)com> wrote:
> On Thu, Dec 10, 2015 at 1:46 PM, oleg yusim <olegyusim(at)gmail(dot)com> wrote:
>
>> Hi David,
>>
>> Can you, please, give me example?
>>
>>
> Not readily...maybe others can. Putting forth specific examples of what
> you want to accomplish may help.
>
> David J.
>
>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | David G. Johnston | 2015-12-10 21:24:22 | Re: Loggingt psql meta-commands |
| Previous Message | David G. Johnston | 2015-12-10 20:50:06 | Re: Loggingt psql meta-commands |