Re: [HACKERS] External Sort timing debug statements

From: Simon Riggs <simon(at)2ndquadrant(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: pgsql-hackers(at)postgresql(dot)org, pgsql-patches(at)postgresql(dot)org
Subject: Re: [HACKERS] External Sort timing debug statements
Date: 2005-10-03 20:28:41
Message-ID: 1128371321.8603.109.camel@localhost.localdomain
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers pgsql-patches

On Mon, 2005-10-03 at 10:36 -0400, Tom Lane wrote:
> Simon Riggs <simon(at)2ndquadrant(dot)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?

Sounds good to me.

Any other requests for info in the trace output.... shout now

Best Regards, Simon Riggs

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Hannu Krosing 2005-10-03 20:32:26 Re: effective SELECT from child tables
Previous Message Jeff Davis 2005-10-03 20:25:00 Re: PG Killed by OOM Condition

Browse pgsql-patches by date

  From Date Subject
Next Message Tom Lane 2005-10-03 22:59:42 Re: External Sort timing debug statements
Previous Message Neil Conway 2005-10-03 20:25:24 Re: cleanup log_disconnections()