PostgreSQL Administration - effects of cancelling a vacuum full

Author

effects of cancelling a vacuum full

Anjan Dave

2006-01-18, 1:24 pm

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?

Thanks,
Anjan

This email message and any included attachments constitute confidential
and privileged information intended exclusively for the listed
addressee(s). If you are not the intended recipient, please notify
Vantage by immediately telephoning 215-579-8390, extension 1158. In
addition, please reply to this message confirming your receipt of the
same in error. A copy of your email reply can also be sent to
mailto:support@vanta
ge.com < blocked::mailto:supp
ort@vantage.com> .
Please do not disclose, copy, distribute or take any action in reliance
on the contents of this information. Kindly destroy all copies of this
message and any attachments. Any other use of this email is prohibited.
Thank you for your cooperation. For more information about Vantage,
please visit our website at http://www.vantage.com.

Scott Marlowe

2006-01-18, 1:24 pm

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 canc
elling 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

Gourish Singbal

2006-01-19, 7:24 am

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@g2switchwor
ks.com> wrote:
>
> On Wed, 2006-01-18 at 12:17, Anjan Dave wrote:
> 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

Jul

2006-01-21, 7:23 am

I ever did what you have done, kill -9 the running process of vacuum
full, because it's not finish until business hour. :)
and the result is i got very mess index and had to dump and restore to
make the database going back good again.

for my best practice, i would like every night a regular vacuum, and
doing old record clean up every month and prepared a second database
server for reporting purpose that's contained all record from all month
back.

and perform a pg_dumpall, drop all database and restore it again every
2 or 3 month.
any suggestion?

Regards,

Jul

Sponsored Links