Re: Extent Locks - Mailing list pgsql-hackers

From Andres Freund
Subject Re: Extent Locks
Date
Msg-id 20130528155333.GD16637@awork2.anarazel.de
Whole thread Raw
In response to Re: Extent Locks  (Stephen Frost <sfrost@snowman.net>)
Responses Re: Extent Locks
Re: Extent Locks
List pgsql-hackers
On 2013-05-28 10:07:06 -0400, Stephen Frost wrote:
> * Jaime Casanova (jaime@2ndquadrant.com) wrote:
> > btw, we can also use a next_extend_blocks GUC/reloption as a limit for
> > autovacuum so it will allow that empty pages at the end of the table
> 
> I'm really not, at all, excited about adding in GUCs for this.

But I thought you were in favor of doing complex stuff like mapping
segments filled somewhere else into place :P

But I agree. This needs to work without much manual intervention. I
think we just need to make autovacuum truncate only if it finds more
free space than whatever amount we might have added at that relation
size plus some slop.

Greetings,

Andres Freund

-- Andres Freund                       http://www.2ndQuadrant.com/PostgreSQL Development, 24x7 Support, Training &
Services



pgsql-hackers by date:

Previous
From: Josh Berkus
Date:
Subject: Re: potential bug in JSON
Next
From: Josh Berkus
Date:
Subject: Re: Planning incompatibilities for Postgres 10.0