Re: Reviewing freeze map code - Mailing list pgsql-hackers

From Andres Freund
Subject Re: Reviewing freeze map code
Date
Msg-id 20160506212016.p57itx2ivjrvb4eu@alap3.anarazel.de
Whole thread Raw
In response to Re: Reviewing freeze map code  (Josh berkus <josh@agliodbs.com>)
Responses Re: Reviewing freeze map code  (Jim Nasby <Jim.Nasby@BlueTreble.com>)
List pgsql-hackers
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.

Andres



pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: ALTER TABLE lock downgrades have broken pg_upgrade
Next
From: Tom Lane
Date:
Subject: Re: Initial release notes created for 9.6