Re: problem with large maintenance_work_mem settings and

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Stefan Kaltenbrunner <stefan(at)kaltenbrunner(dot)cc>
Cc: Simon Riggs <simon(at)2ndquadrant(dot)com>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: problem with large maintenance_work_mem settings and
Date: 2006-03-10 16:49:39
Message-ID: 6435.1142009379@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Stefan Kaltenbrunner <stefan(at)kaltenbrunner(dot)cc> writes:
> samples % symbol name
> 350318533 98.8618 mergepreread
> 971822 0.2743 tuplesort_gettuple_common
> 413674 0.1167 tuplesort_heap_siftup

I'm not immediately seeing why mergepreread would have such a problem
with lots of tapes. Could you reproduce this in a debug build, then
attach to the process with gdb and print out the contents of the "state"
struct?

regards, tom lane

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Zeugswetter Andreas DCP SD 2006-03-10 16:55:10 Re: problem with large maintenance_work_mem settings and
Previous Message Bruce Momjian 2006-03-10 15:53:39 Re: [COMMITTERS] pgsql: Remove Christof Petig copyright on include file,