Re: [COMMITTERS] pgsql: Teach tuplesort.c about "top N" sorting, in which only the first

Поиск
Список
Период
Сортировка
От Jim Nasby
Тема Re: [COMMITTERS] pgsql: Teach tuplesort.c about "top N" sorting, in which only the first
Дата
Msg-id 32346E80-18A2-4FA1-8114-33F74AD7C660@decibel.org
обсуждение исходный текст
Ответ на Re: [COMMITTERS] pgsql: Teach tuplesort.c about "top N" sorting, in which only the first  (Magnus Hagander <magnus@hagander.net>)
Ответы Re: [COMMITTERS] pgsql: Teach tuplesort.c about "top N" sorting, in which only the first  (Magnus Hagander <magnus@hagander.net>)
Список 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@nasby.net
EnterpriseDB      http://enterprisedb.com      512.569.9461 (cell)




В списке pgsql-hackers по дате отправления:

Предыдущее
От: "Andrew Dunstan"
Дата:
Сообщение: Re: Where to hook my custom access control module?
Следующее
От: Magnus Hagander
Дата:
Сообщение: Re: [COMMITTERS] pgsql: Teach tuplesort.c about "top N" sorting, in which only the first