Re: External Sort timing debug statements - Mailing list pgsql-hackers

From Jonah H. Harris
Subject Re: External Sort timing debug statements
Date
Msg-id 36e682920510030746y13d061f2ycca2b131e94e1db2@mail.gmail.com
Whole thread Raw
In response to Re: External Sort timing debug statements  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
I'm not averse to it.  I think it's a good option and I support trace_sort (it really is more of a trace).

On 10/3/05, Tom Lane < tgl@sss.pgh.pa.us> wrote:
Simon Riggs < simon@2ndquadrant.com> writes:
> The following patch implements a fairly light set of timing statements
> aimed at understanding external sort performance. There is no attempt to
> alter the algorithms.

What do people think about putting something like this into 8.1?
Strictly speaking it's a new feature, but the patch seems pretty
noninvasive, and we'd be much more likely to get data points if the
code exists in the mainline release than if people have to patch
their copies.

> postgres=# set debug_sort=true;

I'm a bit inclined to call it trace_sort instead, and to document it
under "Developer Options".  Comments?

                        regards, tom lane

---------------------------(end of broadcast)---------------------------
TIP 2: Don't 'kill -9' the postmaster



--
Respectfully,

Jonah H. Harris, Database Internals Architect
EnterpriseDB Corporation
http://www.enterprisedb.com/

pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: External Sort timing debug statements
Next
From: "Dave Page"
Date:
Subject: Re: [PATCHES] External Sort timing debug statements