From: | Nikolay Samokhvalov <samokhvalov(at)gmail(dot)com> |
---|---|
To: | pgsql-hackers(at)postgresql(dot)org |
Subject: | Full (special) logs for specified users/hosts/etc |
Date: | 2013-05-17 09:29:37 |
Message-ID: | CANNMO+KBKTCu90x+tCJr_tAb1Hj6TUZ9fV_Xd4qi8CWru8A=tA@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Hello hackers,
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?
From | Date | Subject | |
---|---|---|---|
Next Message | Andres Freund | 2013-05-17 09:35:49 | Re: Heap truncation without AccessExclusiveLock (9.4) |
Previous Message | Heikki Linnakangas | 2013-05-17 07:45:26 | Re: Heap truncation without AccessExclusiveLock (9.4) |