Re: [GENERAL] Vacuum and Transactions - Mailing list pgsql-hackers

From Lincoln Yeoh
Subject Re: [GENERAL] Vacuum and Transactions
Date
Msg-id 3.0.5.32.20010707161757.015a5e40@192.228.128.13
Whole thread Raw
In response to Re: [GENERAL] Vacuum and Transactions  (Bruce Momjian <pgman@candle.pha.pa.us>)
Responses Re: Re: [GENERAL] Vacuum and Transactions  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
At 05:59 PM 7/6/01 -0400, Bruce Momjian wrote:
>
>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.

Would 7.2 maintain performance when updating a row repeatedly (update,
commit)? Right now performance goes down in a somewhat 1/x manner. It's
still performs ok but it's nice to have things stay blazingly fast.

If not will the new vacuum restore the performance? 

Or will we have to use the VACUUM FULL?

Thanks,
Link.



pgsql-hackers by date:

Previous
From: Matthew Hagerty
Date:
Subject: Async PQgetResult() question.
Next
From: Lamar Owen
Date:
Subject: Re: Pg on SMP half-powered