| From: | "Shridhar Daithankar" <shridhar_daithankar(at)persistent(dot)co(dot)in> |
|---|---|
| To: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: Learning: Freeing of Unused Records |
| Date: | 2003-06-02 06:44:01 |
| Message-ID: | 3EDB3F89.22975.D8BF628@localhost |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On 26 May 2003 at 12:52, Michael Owens wrote:
> My questions is: when the update commits, and all transactions that depend on
> the version of these (old/updated) tuples all commit, could these tuples be
> automatically marked for reuse during the course of normal processing
> (without adding significant overhead)? --- rather than waiting for a vacuum?
> I am sure the short answer it 'No'.
Well, update is one of the special case. Dead tuples generated can be freed
using vacuum analyze which is not non-blocking and cheaper on resources.. so
you can use it every now and then..
HTH
Bye
Shridhar
--
Captain's Log, star date 21:34.5...
| From | Date | Subject | |
|---|---|---|---|
| Next Message | shreedhar | 2003-06-02 07:16:12 | Re: Error while loading external data into Postgres table. |
| Previous Message | Bodanapu, Sravan | 2003-06-02 06:43:34 | Error while loading external data into Postgres table. |