From: Josh Berkus <josh@agliodbs.com>
To: Andres Freund <andres@2ndquadrant.com>
Cc: pgsql-performance@postgresql.org
Subject: Re: Setting vacuum_freeze_min_age really low
Date: Mon, 13 May 2013 21:02:04 -0700
Message-ID: <5191B73C.9040100@agliodbs.com> (raw)
In-Reply-To: <WM!d3911e74d8025ce3e0363490008cdf150bc66743e81734cb515e41838aa54b886a637f0d5cf6f827c057694522679fa7!@asav-2.01.com>
References: <5150B415.9060907@agliodbs.com>
<CA+TgmoaGT8hE2V=m6G=oB_LfMX1S2xvEE=brgf7W58DSgVWgSQ@mail.gmail.com>
<WM!41efa9246894d9bf23cf32434a08ca088019e273ba110794aabdf7a7dcd5ee174abac60907f6c231c474216042ebeaca!@asav-2.01.com>
<518ED420.4090201@agliodbs.com>
<20130512125027.GA7618@awork2.anarazel.de>
<WM!d3911e74d8025ce3e0363490008cdf150bc66743e81734cb515e41838aa54b886a637f0d5cf6f827c057694522679fa7!@asav-2.01.com>
List-Unsubscribe: <mailto:majordomo@postgresql.org?body=unsub%20pgsql-performance>
HAndres,
> Well. For one you haven't proven that the changed setting actually
> improves performance. So the comparison isn't really valid. We will
I agree that I haven't proven this yet, but that doesn't make it
invalid. Just unproven.
I agree that performance testing is necessary ... and the kind of
performance testing which generated freeze activity, which makes it harder.
> I think you're missing the fact that we don't neccessarily dirty pages,
> just because vacuum visits them. In a mostly insert workload its not
> uncommon that vacuum doesn't change anything. In many scenarios the
Hmmm. But does vacuum visit the pages anyway, in that case?
> b) freezing tuples requires a xlog_heap_freeze wal record to be
> emitted. If we don't freeze, we don't need to emit it.
Oh, that's annoying.
> I think I have said that before, but anyway: I think as long as we need
> to regularly walk the whole relation for correctness there isn't much
> hope to get this into an acceptable state. If we would track the oldest
> xid in a page in a 'freeze map' we could make much of this more
> efficient and way more scalable to bigger data volumes.
Yeah, or come up with some way to eliminate freezing entirely.
--
Josh Berkus
PostgreSQL Experts Inc.
http://pgexperts.com
--
Sent via pgsql-performance mailing list (pgsql-performance@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-performance
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-performance@postgresql.org
Cc: josh@agliodbs.com, andres@2ndquadrant.com
Subject: Re: Setting vacuum_freeze_min_age really low
In-Reply-To: <5191B73C.9040100@agliodbs.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox