From: | Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> |
---|---|
To: | Alvaro Herrera <alvherre(at)commandprompt(dot)com> |
Cc: | JC Praud <brutaltruth42(at)gmail(dot)com>, pgsql-general(at)postgresql(dot)org |
Subject: | Re: auto truncate/vacuum full |
Date: | 2009-10-27 19:02:18 |
Message-ID: | 162867790910271202m78368b4ex7d23c5f205650858@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
2009/10/27 Alvaro Herrera <alvherre(at)commandprompt(dot)com>:
> JC Praud escribió:
>
>> So my question are: can the autovacuum daemon perform vacuum full ? Or
>> another internal postgres process ? Could it come from the TRUNCATE I run
>> and canceled 4 days before ?
>
> No. Autovacuum only issues commands that don't lock tables strongly. I
> doubt this has anything to do with your old TRUNCATE either. My guess
> is that somebody else ran TRUNCATE and forgot to tell you; or maybe an
> automatic external process (cron or some such).
look again on code. I checked it today. When is possible to drop some
pages from end, then vacuum do lock, and try to remove free pages. I
checked it. This process is started from full vacuum, lazy vacuum and
autovacuum too. We have similar issue like JC has.
Regards
Pavel
>
> --
> Alvaro Herrera http://www.CommandPrompt.com/
> PostgreSQL Replication, Consulting, Custom Development, 24x7 support
>
> --
> Sent via pgsql-general mailing list (pgsql-general(at)postgresql(dot)org)
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/pgsql-general
>
From | Date | Subject | |
---|---|---|---|
Next Message | Alvaro Herrera | 2009-10-27 19:39:58 | Re: auto truncate/vacuum full |
Previous Message | Pavel Stehule | 2009-10-27 18:57:52 | Re: Upgrade from 8.2 to 8.3 & catching errors in functions |