This is a discussion on Re: [HACKERS] External Sort timing debug statements within the Pgsql Patches forums, part of the PostgreSQL category; --> Simon Riggs <simon@2ndquadrant.com> writes: > The following patch implements a fairly light set of timing statements > aimed at ...
| |||||||
| FAQ | Members List | Calendar | Search | Today's Posts | Mark Forums Read |
| ||||
| 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 4: Have you searched our list archives? http://archives.postgresql.org |
| |||
| On Mon, Oct 03, 2005 at 10:36:57AM -0400, Tom Lane 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. This would be good > > postgres=# set debug_sort=true; > > I'm a bit inclined to call it trace_sort instead, and to document it > under "Developer Options". Comments? +1 Cheers, D -- David Fetter david@fetter.org http://fetter.org/ phone: +1 510 893 6100 mobile: +1 415 235 3778 Remember to vote! ---------------------------(end of broadcast)--------------------------- TIP 9: In versions below 8.0, the planner will ignore your desire to choose an index scan if your joining column's datatypes do not match |
| ||||
| On Mon, 2005-10-03 at 10:36 -0400, Tom Lane 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? Sounds good to me. Any other requests for info in the trace output.... shout now Best Regards, Simon Riggs ---------------------------(end of broadcast)--------------------------- TIP 3: Have you checked our extensive FAQ? http://www.postgresql.org/docs/faq |