| From: | "Daniel Verite" <daniel(at)manitou-mail(dot)org> |
|---|---|
| To: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: Last modification time of a database? |
| Date: | 2009-03-25 08:28:55 |
| Message-ID: | 3b704b96-31ba-44f5-9eb9-b061457f0661@mm |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Erik Jones wrote:
> These are all client databases at the web hosting company I work at.
> I can't go putting triggers on all of their tables. I think I'll
just
> start taking snapshots of pertinent data from pg_stat_activity and
> after I've been collecting data for a while run a report of dbs that
> haven't seen connections in X long since what I'm really after is
> inactive databases.
Did you think about just setting log_connections to ON and grep'ing the
server logs?
Otherwise it looks like a use-case for ON CONNECT triggers,
unfortunately we don't have them yet.
The TODO list links that message:
http://archives.postgresql.org/pgsql-hackers/2008-03/msg00451.php
Best regards,
--
Daniel
PostgreSQL-powered mail user agent and storage:
http://www.manitou-mail.org
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tim Uckun | 2009-03-25 09:11:53 | Database shut down unexpectedly. |
| Previous Message | berdam | 2009-03-25 02:21:30 | Re: Single missing WAL in long sequence.. |