pg.ddx.io  pgsql-hackers@postgresql.org mailing list archive  

help / color / mirror / Atom feed
From: Jim Nasby <Jim.Nasby@BlueTreble.com>
To: Andres Freund <andres@anarazel.de>
To: Josh berkus <josh@agliodbs.com>
Cc: Joshua D. Drake <jd@commandprompt.com>
Cc: Robert Haas <robertmhaas@gmail.com>
Cc: Masahiko Sawada <sawada.mshk@gmail.com>
Cc: pgsql-hackers@postgresql.org <pgsql-hackers@postgresql.org>
Subject: Re: Reviewing freeze map code
Date: Tue, 10 May 2016 23:38:01 -0500
Message-ID: <a9d2206d-3269-e7f6-4040-8220e85249e4@BlueTreble.com> (raw)
In-Reply-To: <20160506212016.p57itx2ivjrvb4eu@alap3.anarazel.de>
References: <20160506205824.ysst7mk3k26ztok2@alap3.anarazel.de>
	<WM!3c465a785ef366521ed338bb93585bc99a43cc6db976bb0e71111a522ee7f39a31942de6526cb0bccd5f2b7d1678818f!@asav-3.01.com>
	<572D062E.5030308@agliodbs.com>
	<572D068F.3050608@commandprompt.com>
	<20160506210806.f6pnk6ueirjqrlmu@alap3.anarazel.de>
	<WM!795dd98efc24e9727ddfa4f9d6895d1145d958c5eafd1fb31733b556ab1af27dc1b6a3fa1d4968448dec4919a693bf5a!@asav-2.01.com>
	<572D082C.3050704@agliodbs.com>
	<20160506211254.4rknrxpjzav7f66r@alap3.anarazel.de>
	<WM!2dc837b5877ab940f858eb5cd26c9df3c9720e7f64f45a91587c50a6f7e17d8a9a343331e22285a556738bb2a1c9b627!@asav-2.01.com>
	<572D0983.6030109@agliodbs.com>
	<20160506212016.p57itx2ivjrvb4eu@alap3.anarazel.de>
List-Unsubscribe: <mailto:majordomo@postgresql.org?body=unsub%20pgsql-hackers>

On 5/6/16 4:20 PM, Andres Freund wrote:
> On 2016-05-06 14:15:47 -0700, Josh berkus wrote:
>> For the serious testing, does anyone have a good technique for creating
>> loads which would stress-test vacuum freezing?  It's hard for me to come
>> up with anything which wouldn't be very time-and-resource intensive
>> (like running at 10,000 TPS for a week).
>
> I've changed the limits for freezing options a while back, so you can
> now set autovacuum_freeze_max as low as 100000 (best set
> vacuum_freeze_table_age accordingly).  You'll have to come up with a
> workload that doesn't overwrite all data continuously (otherwise
> there'll never be old rows), but otherwise it should now be fairly easy
> to test that kind of scenario.

There's also been a tool for forcibly advancing XID floating around for 
quite some time. Using that could have the added benefit of verifying 
anti-wrap still works correctly. (Might be worth testing mxid wrap too...)
-- 
Jim Nasby, Data Architect, Blue Treble Consulting, Austin TX
Experts in Analytics, Data Architecture and PostgreSQL
Data in Trouble? Get it in Treble! http://BlueTreble.com
855-TREBLE2 (855-873-2532)   mobile: 512-569-9461


-- 
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers



view thread (256+ messages)  latest in thread

Message-ID: <a9d2206d-3269-e7f6-4040-8220e85249e4@BlueTreble.com>
Permalink:  ../a9d2206d-3269-e7f6-4040-8220e85249e4@BlueTreble.com/
Also on:    postgresql.org/message-id/a9d2206d-3269-e7f6-4040-8220e85249e4@BlueTreble.com

 · 

reply
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-hackers@postgresql.org
  Cc: Jim.Nasby@BlueTreble.com, andres@anarazel.de, josh@agliodbs.com, jd@commandprompt.com, robertmhaas@gmail.com, sawada.mshk@gmail.com
  Subject: Re: Reviewing freeze map code
  In-Reply-To: <a9d2206d-3269-e7f6-4040-8220e85249e4@BlueTreble.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