Re: auto truncate/vacuum full - Mailing list pgsql-general

From Pavel Stehule
Subject Re: auto truncate/vacuum full
Date
Msg-id 162867790910271202m78368b4ex7d23c5f205650858@mail.gmail.com
Whole thread Raw
In response to Re: auto truncate/vacuum full  (Alvaro Herrera <alvherre@commandprompt.com>)
Responses Re: auto truncate/vacuum full  (Alvaro Herrera <alvherre@commandprompt.com>)
List pgsql-general
2009/10/27 Alvaro Herrera <alvherre@commandprompt.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@postgresql.org)
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/pgsql-general
>

pgsql-general by date:

Previous
From: Pavel Stehule
Date:
Subject: Re: Upgrade from 8.2 to 8.3 & catching errors in functions
Next
From: VladK
Date:
Subject: PHP + PDO + PGPOOL = Segmentation fault