Skip site navigation (1) Skip section navigation (2)

Re: Have vacuum emit a warning when it runs out of maintenance_work_mem

From: Heikki Linnakangas <heikki(at)enterprisedb(dot)com>
To: "Jim C(dot) Nasby" <decibel(at)decibel(dot)org>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, "Jim C(dot) Nasby" <jim(at)nasby(dot)net>, Robert Treat <xzilla(at)users(dot)sourceforge(dot)net>, pgsql-patches(at)postgresql(dot)org, Guillaume Smet <guillaume(dot)smet(at)gmail(dot)com>
Subject: Re: Have vacuum emit a warning when it runs out of maintenance_work_mem
Date: 2007-05-14 16:48:18
Message-ID: 464892D2.3050705@enterprisedb.com (view raw or flat)
Thread:
Lists: pgsql-patches
Jim C. Nasby wrote:
> Did someone come up with a bitmap compression scheme for on-disk bitmap
> indexes that would help out here? Some form of compression could make a
> big difference in mostly-dead pages. 

Yes, there's a pretty nice compression scheme there, but the requirement 
for random access makes it a bit hard to use in this case.

> If nothing else, it would likely be
> worth special-casing an entire page being dead, which is a common case
> for queue tables. That could be done by making an entry in the page
> number array with a special offset value.

That won't work, because someone might add live tuples to the page after 
the 1st vacuum pass. You could only invoke that special case when 
there's no room on the page for new tuples, but that's a hack and not as 
common.

-- 
   Heikki Linnakangas
   EnterpriseDB   http://www.enterprisedb.com

In response to

Responses

pgsql-patches by date

Next:From: Tom LaneDate: 2007-05-14 16:54:08
Subject: Re: Have vacuum emit a warning when it runs out of maintenance_work_mem
Previous:From: Jim C. NasbyDate: 2007-05-14 16:45:25
Subject: Re: Concurrent psql patch

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group