On Sat, Mar 26, 2011 at 2:30 PM, Jan Wieck <janwi...@yahoo.com> wrote:
> My current idea for a fix is to modify lazy_truncate_heap(). It does acquire > and release the exclusive lock, so it should be possible to do this in > smaller chunks, releasing and reacquiring the lock so that client > transactions can get their work done as well. Agreed, presumably with vacuum delay in there as well? > At the same time I would > change count_nondeletable_pages() so that it uses a forward scan direction > (if that leads to a speedup). Do we need that? Linux readahead works in both directions doesn't it? Guess it wouldn't hurt too much. BTW does it read the blocks at that point using a buffer strategy? -- Simon Riggs http://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Training & Services -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
