Re: (auto)vacuum truncate exclusive lock - Mailing list pgsql-hackers

From Alvaro Herrera
Subject Re: (auto)vacuum truncate exclusive lock
Date
Msg-id 20130412180826.GI30671@eldon.alvh.no-ip.org
Whole thread Raw
In response to Re: (auto)vacuum truncate exclusive lock  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: (auto)vacuum truncate exclusive lock
List pgsql-hackers
Tom Lane escribió:

> Are you saying you intend to revert that whole concept?  That'd be
> okay with me, I think.  Otherwise we need some thought about how to
> inform the stats collector what's really happening.

Maybe what we need is to consider table truncation as a separate
activity from vacuuming.  Then autovacuum could invoke it without having
to do a full-blown vacuum.  For this to work, I guess we would like to
separately store the status of the back-scan in pgstat somehow (I think
a boolean flag suffices: "were we able to truncate all pages that
appeared to be empty?")

--
Álvaro Herrera                http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services



pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: (auto)vacuum truncate exclusive lock
Next
From: Stephen Frost
Date:
Subject: Re: Detach/attach table and index data files from one cluster to another