Re: pgsql: Make large sequential scans and VACUUMs work in a limited-size

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Teodor Sigaev <teodor(at)sigaev(dot)ru>
Cc: pgsql-committers(at)postgresql(dot)org
Subject: Re: pgsql: Make large sequential scans and VACUUMs work in a limited-size
Date: 2007-05-31 13:47:38
Message-ID: 28887.1180619258@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers pgsql-hackers

Teodor Sigaev <teodor(at)sigaev(dot)ru> writes:
>> Work not done in this commit: teach GiST and GIN indexes to use the vacuum
>> BufferAccessStrategy for vacuum-driven fetches.

> Attached patch does it. Patch is rather simple - it just replaces ReadBuffer to
> ReadBufferWithStrategy in all vacuum-involved places.

Thanks --- I figured you could fix that much faster than I could ;-)

regards, tom lane

In response to

Browse pgsql-committers by date

  From Date Subject
Next Message Teodor Sigaev 2007-05-31 14:03:09 pgsql: Replace ReadBuffer to ReadBufferWithStrategy in all
Previous Message Teodor Sigaev 2007-05-31 13:42:04 Re: pgsql: Make large sequential scans and VACUUMs work in a limited-size

Browse pgsql-hackers by date

  From Date Subject
Next Message Werner Echezuria 2007-05-31 13:58:27 SQLF Optimization question
Previous Message Teodor Sigaev 2007-05-31 13:42:04 Re: pgsql: Make large sequential scans and VACUUMs work in a limited-size