| From: | Jim Nasby <decibel(at)decibel(dot)org> |
|---|---|
| To: | Magnus Hagander <magnus(at)hagander(dot)net> |
| Cc: | Alvaro Herrera <alvherre(at)commandprompt(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: [COMMITTERS] pgsql: Teach tuplesort.c about "top N" sorting, in which only the first |
| Date: | 2007-05-09 15:55:12 |
| Message-ID: | 32346E80-18A2-4FA1-8114-33F74AD7C660@decibel.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-committers pgsql-hackers |
On May 8, 2007, at 2:24 PM, Magnus Hagander wrote:
> Speaking of which, it might be interesting to actually show these
> values
> in the stats collector. I was thinking three cols for each database
> (probably the best level?) that counts each of those three
> counters. If
> you have a lot of sorts (percentage-wise) spilling to disk, it is
> often
> something you want to investigate, so exposing it that way seems
> like a
> good thing.
What 3 columns? In-memory sorts, on-disk sorts, and on-disk size?
(Sum of how much spilled to disk).
I agree that per-database makes sense, though I'd settle for per-
cluster.
--
Jim Nasby jim(at)nasby(dot)net
EnterpriseDB http://enterprisedb.com 512.569.9461 (cell)
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Magnus Hagander | 2007-05-09 16:01:52 | Re: [COMMITTERS] pgsql: Teach tuplesort.c about "top N" sorting, in which only the first |
| Previous Message | User Cunha17 | 2007-05-09 15:44:39 | snapshot - src: Documentation of the "CREATE SNAPSHOT LOG" WITH clause. |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Magnus Hagander | 2007-05-09 16:01:52 | Re: [COMMITTERS] pgsql: Teach tuplesort.c about "top N" sorting, in which only the first |
| Previous Message | Karel Gardas | 2007-05-09 14:41:42 | Where to hook my custom access control module? |