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

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Jim Nasby <decibel(at)decibel(dot)org>
Cc: Magnus Hagander <magnus(at)hagander(dot)net>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: [COMMITTERS] pgsql: Teach tuplesort.c about "top N" sorting, in which only the first
Date: 2007-05-06 14:32:14
Message-ID: 8225.1178461934@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers pgsql-hackers

Jim Nasby <decibel(at)decibel(dot)org> writes:
> There's several problems with that. First, trace_sort isn't
> documented (or at least it's not in postgresql.conf), so most folks
> don't know it exists. Second, in order to see it's output you have to
> drop log_min_messages to debug. That results in a huge log volume,
> especially on a production system.

Nonsense ... trace_sort output is at LOG level.

regards, tom lane

In response to

Responses

Browse pgsql-committers by date

  From Date Subject
Next Message Jim Nasby 2007-05-06 14:56:24 Re: [COMMITTERS] pgsql: Teach tuplesort.c about "top N" sorting, in which only the first
Previous Message Magnus Hagander 2007-05-06 07:17:20 Re: pgsql: Check return code from strxfrm on Windows since it has a

Browse pgsql-hackers by date

  From Date Subject
Next Message Jim Nasby 2007-05-06 14:39:42 Re: Integer datetimes
Previous Message Jim Nasby 2007-05-06 14:26:54 Re: New idea for patch tracking