Re: Autovacuum fails to keep visibility map up-to-date in mostly-insert-only-tables - Mailing list pgsql-hackers

From Josh Berkus
Subject Re: Autovacuum fails to keep visibility map up-to-date in mostly-insert-only-tables
Date
Msg-id 5445AC2E.7030302@agliodbs.com
Whole thread Raw
In response to Autovacuum fails to keep visibility map up-to-date in mostly-insert-only-tables  (Alexey Bashtanov <bashtanov@imap.cc>)
Responses Re: Autovacuum fails to keep visibility map up-to-date in mostly-insert-only-tables
List pgsql-hackers
On 10/20/2014 05:39 PM, Jim Nasby wrote:
> Or maybe vacuum isn't the right way to handle some of these scenarios.
> It's become the catch-all for all of this stuff, but maybe that doesn't
> make sense anymore. Certainly when it comes to dealing with inserts
> there's no reason we *have* to do anything other than set hint bits and
> possibly freeze xmin.

+1

-- 
Josh Berkus
PostgreSQL Experts Inc.
http://pgexperts.com



pgsql-hackers by date:

Previous
From: Jim Nasby
Date:
Subject: Re: Autovacuum fails to keep visibility map up-to-date in mostly-insert-only-tables
Next
From: Jim Nasby
Date:
Subject: Re: Proposal: Log inability to lock pages during vacuum