Skip site navigation (1) Skip section navigation (2)

Peripheral Links

Header And Logo

PostgreSQL
| The world's most advanced open source database.

Site Navigation

Search for
  Advanced Search

Re: sort_mem statistics ...


  • From: Simon Riggs <simon(at)2ndquadrant(dot)com>
  • To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
  • Cc: "Marc G. Fournier" <scrappy(at)postgresql(dot)org>, pgsql-hackers(at)postgresql(dot)org
  • Subject: Re: sort_mem statistics ...
  • Date: Mon, 24 Oct 2005 23:24:32 +0100
  • Message-id: <1130192672(dot)8300(dot)1102(dot)camel(at)localhost(dot)localdomain>

On Tue, 2005-10-18 at 18:57 -0400, Tom Lane wrote:
> "Marc G. Fournier" <scrappy(at)postgresql(dot)org> writes:
> > On Tue, 18 Oct 2005, Tom Lane wrote:
> >> Looking at the code, I notice that the messages are all emitted at level 
> >> NOTICE.  Perhaps that was not such a good idea --- it'd be pretty much 
> >> in-your-face if it were on all the time.  Does anyone think it'd be a 
> >> good idea to emit the trace_sort messages at level LOG, instead?
> 
> > If someone sets trace_sort, does it matter what level its emit'd at?
> 
> Well, yeah.  It depends whether you are thinking of the trace feature as
> being used interactively, or as something turned on to gather data over
> time in a production installation.  In the second case you'd want the
> info to go to the postmaster log, but not want to see it dumped on your
> terminal all the time ...

Yes, please set this at LOG.

It will certainly provide many more data points for us to analyse.

Best Regards, Simon Riggs




Home | Main Index | Thread Index

Privacy Policy | PostgreSQL Archives hosted by Command Prompt, Inc. | Designed by tinysofa
Copyright © 1996 – 2008 PostgreSQL Global Development Group