From: | Gourish Singbal <gourish(at)gmail(dot)com> |
---|---|
To: | Anjan Dave <adave(at)vantage(dot)com> |
Cc: | Scott Marlowe <smarlowe(at)g2switchworks(dot)com>, pgsql-admin(at)postgresql(dot)org |
Subject: | Re: effects of cancelling a vacuum full |
Date: | 2006-01-19 10:40:54 |
Message-ID: | 674d1f8a0601190240x17d44701td800f765aaab70de@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
One Question out of curiosity .. How did u cancel the vacuum full ?.
1. killed the process id .. eg using kill -9
2. canceled the vacuum full from command prompt eg using "ctrl C".
3. or did an immediate shutdown .
On 1/18/06, Scott Marlowe <smarlowe(at)g2switchworks(dot)com> wrote:
>
> On Wed, 2006-01-18 at 12:17, Anjan Dave wrote:
> > Hi,
> >
> > I just had to cancel one VACUUM FULL (of a 4.3m row table) that someone
> ran in business hours. It was after an hour or so that I realized, and it
> was blocking queries, running out of connections, so I cancelled it. Are
> there any bad side effects of cancelling an ongoing full vacuum of a table
> or a database? Does a partial full vacuum give back any space?
> >
>
> No damage done.
> No space returned.
> Just wait and run it again later.
> Tell your used to do a vacuum regular during business hours or you'll
> have to give him a stern talking to.
>
> ---------------------------(end of broadcast)---------------------------
> TIP 9: In versions below 8.0, the planner will ignore your desire to
> choose an index scan if your joining column's datatypes do not
> match
>
--
Best,
Gourish Singbal
From | Date | Subject | |
---|---|---|---|
Next Message | Chris Jewell | 2006-01-19 10:44:35 | WAL log archive frequency |
Previous Message | sandhya | 2006-01-19 08:23:07 | Re: Fw: lo_import problem |