Re: problem with large maintenance_work_mem settings and - Mailing list pgsql-hackers

From Tom Lane
Subject Re: problem with large maintenance_work_mem settings and
Date
Msg-id 16339.1141589703@sss.pgh.pa.us
Whole thread Raw
In response to problem with large maintenance_work_mem settings and CREATE INDEX  (Stefan Kaltenbrunner <stefan@kaltenbrunner.cc>)
Responses Re: problem with large maintenance_work_mem settings and  (Simon Riggs <simon@2ndquadrant.com>)
Re: problem with large maintenance_work_mem settings and  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
Stefan Kaltenbrunner <stefan@kaltenbrunner.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
availableblock number). This could    * get fairly slow if there were many free blocks, but we don't expect    * there
tobe 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


pgsql-hackers by date:

Previous
From: "Markus Bertheau"
Date:
Subject: pg.conf re-reading in signal handler or at next return to main loop?
Next
From: Tom Lane
Date:
Subject: Re: [PATCHES] LDAP auth