| From: | Andres Freund <andres(at)2ndquadrant(dot)com> |
|---|---|
| To: | Stephen Frost <sfrost(at)snowman(dot)net> |
| Cc: | Jaime Casanova <jaime(at)2ndquadrant(dot)com>, Craig Ringer <craig(at)2ndquadrant(dot)com>, Robert Haas <robertmhaas(at)gmail(dot)com>, Heikki Linnakangas <hlinnakangas(at)vmware(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Extent Locks |
| Date: | 2013-05-28 15:53:33 |
| Message-ID: | 20130528155333.GD16637@awork2.anarazel.de |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 2013-05-28 10:07:06 -0400, Stephen Frost wrote:
> * Jaime Casanova (jaime(at)2ndquadrant(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Josh Berkus | 2013-05-28 15:56:31 | Re: Planning incompatibilities for Postgres 10.0 |
| Previous Message | Josh Berkus | 2013-05-28 15:53:24 | Re: potential bug in JSON |