From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | "Campbell, Lance" <lance(at)illinois(dot)edu> |
Cc: | "pgsql-admin(at)postgresql(dot)org" <pgsql-admin(at)postgresql(dot)org> |
Subject: | Re: Possible request for new feature |
Date: | 2014-11-05 15:39:36 |
Message-ID: | 3374.1415201976@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
"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 | Campbell, Lance | 2014-11-05 16:15:50 | Re: Possible request for new feature |
Previous Message | Campbell, Lance | 2014-11-05 15:25:49 | Possible request for new feature |