From: | John Murtari <jmurtari(at)thebook(dot)com> |
---|---|
To: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
Cc: | pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: Patch set under development to add usage reporting. |
Date: | 2009-10-31 22:47:32 |
Message-ID: | 19180.48772.804345.600468@torch.softwareworkshop.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Peter
> > I had taken a look at existing statistics reporting (at
> > least in the 7.4.x tree) and didn't see a good analog to what this
> > provides.
>
> The statistics collector detailed at
> <http://www.postgresql.org/docs/7.4/interactive/monitoring-stats.html>
> appears to do pretty much the same, although on a slightly lower level.
> But that's the logical place where to add that in PostgreSQL.
>
> > We had proposed this as a comment on an earlier version of
> > the standard. From discussion with some senior committee members,
> > it would appear the best fit for this type of capability might
> > be in the INFORMATION SCHEMA part of the standard. We also had
> > developed the "SHOW STATISTICS" syntax for DB version that don't
> > support INFORMATION SCHEMA.
>
> I don't really get the point of the SHOW STATISTICS command. There is
> already a command whose purpose is to retrieve data in tabular form,
> namely SELECT.
Okay, thank you. We will take another look at those items.
Best regards!
--
John
____________________________________________________________________
John Murtari Software Workshop Inc.
jmurtari(at)thebook(dot)com "software that fits!" (TM)
(315) 944-0999 (x-211) http://www.SoftwareWorkshop.com/
From | Date | Subject | |
---|---|---|---|
Next Message | John Murtari | 2009-10-31 22:50:39 | Re: Patch set under development to add usage reporting. |
Previous Message | Robert Haas | 2009-10-31 21:12:43 | Re: WIP: push AFTER-trigger execution into ModifyTable node |