Re: Full (special) logs for specified users/hosts/etc - Mailing list pgsql-hackers

From Victor Yegorov
Subject Re: Full (special) logs for specified users/hosts/etc
Date
Msg-id CAGnEbohtpbgWRbQspuMCXVZ3RgRWqNyUzApuR4DbdhhMWOnJhA@mail.gmail.com
Whole thread Raw
In response to Full (special) logs for specified users/hosts/etc  (Nikolay Samokhvalov <samokhvalov@gmail.com>)
List pgsql-hackers
2013/5/17 Nikolay Samokhvalov <samokhvalov@gmail.com>
Consider a Postgres cluster containing several DBs (for example several projects/sites). If one wants to optimize queries on one specified site -- what should he do? His obvious need is to switch full logging for the exact database on, collect the logs and analyze them using pgFouine/pgBadger.

But currently, there is no way to specify log settings for one database / one user / one host. There are only *global* settings in postgres.conf.

We experienced this problem in various project several times already. Usually it is  solved with initdb-ing separate cluster, what is annoying and difficult if you have replication installed and working.

How difficult is to implement *local* logging settings per database/user/host? Is it worth to work on for future versions?

Not exactly suitable for pgBadger, but one could setup “csvlog” format, load logs into the dedicated table and analyse with SQL statements:

pgsql-hackers by date:

Previous
From: Andres Freund
Date:
Subject: Re: Heap truncation without AccessExclusiveLock (9.4)
Next
From: Cédric Villemain
Date:
Subject: Re: [GENERAL] PLJava for Postgres 9.2.