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: Michael Paesold <mpaesold(at)gmx(dot)at>, hubert depesz lubaczewski <depesz(at)gmail(dot)com>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: problem with large maintenance_work_mem settings and
Date: 2006-03-05 20:15:03
Message-ID: 16339.1141589703@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
> 24915704 96.2170 ltsReleaseBlock
> 387265 1.4955 LogicalTapeRead
> 168725 0.6516 inlineApplySortFunction

Hmm ... the comment in ltsReleaseBlock sez

/*
* Insert blocknum into array, preserving decreasing order (so that
* ltsGetFreeBlock returns the lowest available block number). This could
* get fairly slow if there were many free blocks, but we don't expect
* there to be very many at one time.
*/

We probably need to tweak things so this doesn't get called during the
"final merge" pass. Looking at it now.

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2006-03-05 20:20:43 Re: [PATCHES] LDAP auth
Previous Message Markus Bertheau 2006-03-05 20:14:52 pg.conf re-reading in signal handler or at next return to main loop?