> Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> writes:
> >> In 7.2, VACUUM will not require an exclusive lock.
> > Care to elaborate on that? How are you going to do it?
> Uh, have you not been paying attention to pg-hackers for the
> last two months?
> I am assuming here that concurrent VACUUM will become the default
> kind of vacuum, and the old style will be invoked by some other
> syntax (VACUUM FULL ..., maybe).
OK, I just talked to Tom on the phone and here is his idea for 7.2. He
says he already posted this, but I missed it.
His idea is that in 7.2 VACUUM will only move rows within pages. It
will also store unused space locations into shared memory to be used by
backends needing to add rows to tables. Actual disk space compaction
will be performed by new a VACUUM FULL(?) command.
The default VACUUM will not lock the table but only prevent the table
from being dropped.
Bruce Momjian | http://candle.pha.pa.us
pgman(at)candle(dot)pha(dot)pa(dot)us | (610) 853-3000
+ If your life is a hard drive, | 830 Blythe Avenue
+ Christ can be your backup. | Drexel Hill, Pennsylvania 19026
In response to
pgsql-hackers by date
|Next:||From: David Bennett||Date: 2001-07-06 22:44:21|
|Subject: RE: New SQL Datatype RECURRINGCHAR |
|Previous:||From: Vitalino||Date: 2001-07-06 19:12:28|
|Subject: Problem with authentication in psql.|
pgsql-general by date
|Next:||From: Mark G. Franz||Date: 2001-07-06 22:14:30|
|Subject: Grab data WHERE table.ID NOT LIKE otherTable.ID|
|Previous:||From: Spiros Ioannou||Date: 2001-07-06 21:30:22|
|Subject: postgres slower than grep?|