From: | Stephen Frost <sfrost(at)snowman(dot)net> |
---|---|
To: | Jaime Casanova <jaime(at)2ndquadrant(dot)com> |
Cc: | 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 14:07:06 |
Message-ID: | 20130528140705.GD8597@tamriel.snowman.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
* 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. We just
need to realize when the only available space in the relation is at the
end and people are writing to it and avoid truncating pages off the end-
if we don't already have locks that prevent vacuum from doing this
already. I'd want to see where it's actually happening before stressing
over it terribly much.
Thanks,
Stephen
From | Date | Subject | |
---|---|---|---|
Next Message | Robert Haas | 2013-05-28 14:15:10 | Re: getting rid of freezing |
Previous Message | Robert Haas | 2013-05-28 14:05:53 | Re: [BUGS] COPY .... (FORMAT binary) syntax doesn't work |