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 23:20:59
Message-ID: 22094.1142032859@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

I wrote:
> 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 don't have enough memory to really reproduce this, but I've come close
> enough that I believe I see what's happening. It's an artifact of the
> code I added recently to prevent the SortTuple array from growing during
> the merge phase, specifically the "mergeslotsfree" logic.

I've committed a fix for this; if you're still interested, please
retest.

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Ragnar 2006-03-10 23:21:35 Re: Proposal for SYNONYMS
Previous Message Tom Lane 2006-03-10 21:51:35 Re: Proposal for SYNONYMS