| From: | "pgAdmin Trac" <trac(at)code(dot)pgadmin(dot)org> |
|---|---|
| To: | |
| Cc: | pgadmin-hackers(at)postgresql(dot)org |
| Subject: | [pgAdmin III] #117: Explain Buffers |
| Date: | 2009-12-20 22:45:01 |
| Message-ID: | 045.e4d5259716b61e1fb98c881eecb3adfb@code.pgadmin.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgadmin-hackers |
#117: Explain Buffers
---------------------------+------------------------------------------------
Reporter: gleu | Owner: dpage
Type: feature | Status: new
Priority: minor | Milestone:
Component: pgadmin | Version: trunk
Keywords: querytool 8.5 | Platform: all
---------------------------+------------------------------------------------
There is a new option in EXPLAIN statement to get new informations:
buffers read/hit. That information should be available in the query tool
when one uses the EXPLAIN feature of the query tool.
See https://commitfest.postgresql.org/action/patch_view?id=194 for more
details.
--
Ticket URL: <http://code.pgadmin.org/trac/ticket/117>
pgAdmin III <http://code.pgadmin.org/trac/>
pgAdmin III
| From | Date | Subject | |
|---|---|---|---|
| Next Message | pgAdmin Trac | 2009-12-20 22:48:20 | [pgAdmin III] #118: Operator Exclusion Constraints |
| Previous Message | pgAdmin Trac | 2009-12-20 22:41:43 | Re: [pgAdmin III] #116: Application Name |