Skip site navigation (1)
Skip section navigation (2)
Peripheral Links
Header And Logo
|
Site Navigation
Re: How to make lazy VACUUM of one table run in several transactions ?
- From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
- To: Alvaro Herrera <alvherre(at)dcc(dot)uchile(dot)cl>
- Cc: Hannu Krosing <hannu(at)tm(dot)ee>, pgsql-hackers(at)postgresql(dot)org
- Subject: Re: How to make lazy VACUUM of one table run in several transactions ?
- Date: Mon, 25 Apr 2005 11:11:45 -0400
- Message-id: <19162(dot)1114441905(at)sss(dot)pgh(dot)pa(dot)us>
Alvaro Herrera <alvherre(at)dcc(dot)uchile(dot)cl> writes: > On Sun, Apr 24, 2005 at 12:02:37PM +0300, Hannu Krosing wrote: >> Must some locks also be released an reaquired inside this loop, or is >> there something else I should keep in mind when trying to do this ? > There is "session lock" on the table. You must release that. Actually, the only hope of making this work is NOT to release that. If you hold the appropriate lock at the session level then it is reasonable to consider successive transactions within the vacuum as being one big operation. I think the major issue with this would be memory management, ie, how to prevent CommitTransactionCommand from cleaning up all of vacuum's working state. regards, tom lane
- Follow-Ups:
- Re: How to make lazy VACUUM of one table run in several
- From: Hannu Krosing
- Re: How to make lazy VACUUM of one table run in several
- References:
- How to make lazy VACUUM of one table run in several transactions ?
- From: Hannu Krosing
- Re: How to make lazy VACUUM of one table run in several transactions ?
- From: Alvaro Herrera
- How to make lazy VACUUM of one table run in several transactions ?
- Prev by Date: Re: How to make lazy VACUUM of one table run in several transactions ?
- Next by Date: Re: [PERFORM] Bad n_distinct estimation; hacks suggested?
- Previous by thread: Re: How to make lazy VACUUM of one table run in several transactions ?
- Next by thread: Re: How to make lazy VACUUM of one table run in several
- Indexes: