Re: Extent Locks - Mailing list pgsql-hackers

From Jaime Casanova
Subject Re: Extent Locks
Date
Msg-id CAJKUy5iGVyLxDMJ+vvYV9zjhTS+Djz=+oY+eXb701za_htEDog@mail.gmail.com
Whole thread Raw
In response to Re: Extent Locks  (Stephen Frost <sfrost@snowman.net>)
Responses Re: Extent Locks  (Jaime Casanova <jaime@2ndquadrant.com>)
List pgsql-hackers
On Tue, May 28, 2013 at 7:36 AM, Stephen Frost <sfrost@snowman.net> wrote:
>
> On the other hand, I do feel like people are worried about
> over-extending a relation and wasting disk space- but with the way that
> vacuum can clean up pages at the end, that would only be a temporary
> situation anyway.
>

Hi,

Maybe i'm wrong but this should be easily solved by an
autovacuum_no_truncate_empty_pages or an autovacuum_empty_pages_limit
GUC/reloption.
Just to clarify the second one autovacuum will allow until that limit
of empty pages, and will remove excess from there

We can also think in GUC/reloption for next_extend_blocks so formula
is needed, or of course the automated calculation that has been
proposed

--
Jaime Casanova         www.2ndQuadrant.com
Professional PostgreSQL: Soporte 24x7 y capacitación
Phone: +593 4 5107566         Cell: +593 987171157



pgsql-hackers by date:

Previous
From: Bruce Momjian
Date:
Subject: Re: ASYNC Privileges proposal
Next
From: Robert Haas
Date:
Subject: Re: MVCC catalog access