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

Re: Automatic free space map filling

From: Peter Eisentraut <peter_e(at)gmx(dot)net>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: Automatic free space map filling
Date: 2006-03-01 16:16:16
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-hackers
Am Montag, 27. Februar 2006 19:42 schrieb Tom Lane:
> The free-space map is not the hard part of the problem.  You still have
> to VACUUM --- that is, wait until the dead tuple is not only committed
> dead but is certainly dead to all onlooker transactions, and then remove
> its index entries as well as the tuple itself.  The first part of this
> makes it impossible for a transaction to be responsible for vacuuming
> its own detritus.

I'm not sure if I made myself clear.  The idea is that you fill the free-space 
map early with opportunitistic entries in the hope that most updates and 
deletes go through "soon".  That is, these entries will be invalid for a 
short time but hopefully by the time another write looks at them, the entries 
will have become valid.  That way you don't actually have to run vacuum on 
these deleted rows.

Peter Eisentraut

In response to


pgsql-hackers by date

Next:From: Kevin GrittnerDate: 2006-03-01 16:22:45
Subject: Re: Vacuum dead tuples that are "between"
Previous:From: Michael FuhrDate: 2006-03-01 16:10:59
Subject: Re: Reg:lo_open error..pls help me

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