From: | "Campbell, Lance" <lance(at)illinois(dot)edu> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | "pgsql-admin(at)postgresql(dot)org" <pgsql-admin(at)postgresql(dot)org> |
Subject: | Re: Possible request for new feature |
Date: | 2014-11-05 16:15:50 |
Message-ID: | B75CD08C73BD3543B97E4EF3964B7D701FC789C4@CITESMBX1.ad.uillinois.edu |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
Tom,
Thanks so much. That was very useful. It is more useful than my suggested enhancement.
Thanks,
Lance Campbell
Software Architect
Web Services at Public Affairs
217-333-0382
-----Original Message-----
From: Tom Lane [mailto:tgl(at)sss(dot)pgh(dot)pa(dot)us]
Sent: Wednesday, November 05, 2014 9:40 AM
To: Campbell, Lance
Cc: pgsql-admin(at)postgresql(dot)org
Subject: Re: [ADMIN] Possible request for new feature
"Campbell, Lance" <lance(at)illinois(dot)edu> writes:
> I develop web application for the University of Illinois. We use PostgreSQL on the backend to provide our web application with data for around 3 million pages of dynamic web content per month. A nice feature would be the ability to do something just like EXPLAIN ANALYZE on queries with the slight difference of actually returning the results from the query and appending the QUERY PLAN to the end of the query.
Such a behavior would break just about every client application. Have you looked into using the auto_explain module, which instead logs query plans to the postmaster log? That's a far less invasive way of collecting plans for queries of live applications. pg_stat_statements would be worth a look too.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Alex Lai | 2014-11-06 13:41:29 | Use up too much memory |
Previous Message | Tom Lane | 2014-11-05 15:39:36 | Re: Possible request for new feature |