From: | Andres Freund <andres(at)2ndquadrant(dot)com> |
---|---|
To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
Cc: | Josh Berkus <josh(at)agliodbs(dot)com>, postgres performance list <pgsql-performance(at)postgresql(dot)org> |
Subject: | Re: Setting vacuum_freeze_min_age really low |
Date: | 2013-05-09 17:22:05 |
Message-ID: | 20130509172205.GB27844@awork2.anarazel.de |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-performance |
On 2013-05-09 12:09:04 -0400, Robert Haas wrote:
> On Mon, Mar 25, 2013 at 4:31 PM, Josh Berkus <josh(at)agliodbs(dot)com> wrote:
> > In the past, setting vacuum_freeze_min_age (vfma) really low (say to
> > 10000 or 50000) would have caused lots of extra writing work due to
> > dirtying extra pages for freezing. This has been our stated reason to
> > keep vfma high, despite the obvious advantage of freezing tuples while
> > they're still in the cache.
>
> That, and Tom's concern about forensics, which I understand to be the
> larger sticking point.
FWIW I found having sensible xmin/xmax repeatedly really useful for
debugging problems. Most problems don't get noticed within minutes so
loosing evidence that fast is bad.
Greetings,
Andres Freund
--
Andres Freund http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
--
Sent via pgsql-performance mailing list (pgsql-performance(at)postgresql(dot)org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-performance
From | Date | Subject | |
---|---|---|---|
Next Message | Vitalii Tymchyshyn | 2013-05-10 10:48:49 | Re: In progress INSERT wrecks plans on table |
Previous Message | Andres Freund | 2013-05-09 17:18:39 | Re: Setting vacuum_freeze_min_age really low |