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

help / color / mirror / Atom feed
From: Josh berkus <josh@agliodbs.com>
To: Andres Freund <andres@anarazel.de>
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: Fri, 6 May 2016 14:15:47 -0700
Message-ID: <572D0983.6030109@agliodbs.com> (raw)
In-Reply-To: <WM!2dc837b5877ab940f858eb5cd26c9df3c9720e7f64f45a91587c50a6f7e17d8a9a343331e22285a556738bb2a1c9b627!@asav-2.01.com>
References: <572D0309.4090402@commandprompt.com>
	<20160506205012.ipuhvctss2ozzs6m@alap3.anarazel.de>
	<572D0471.3040009@commandprompt.com>
	<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>
List-Unsubscribe: <mailto:majordomo@postgresql.org?body=unsub%20pgsql-hackers>

On 05/06/2016 02:12 PM, Andres Freund wrote:
> On 2016-05-06 14:10:04 -0700, Josh berkus wrote:
>> On 05/06/2016 02:08 PM, Andres Freund wrote:
>>
>>> It bothers me more than it probably should: Nobdy tests, reviews,
>>> whatever a complex patch with significant data-loss potential. But as
>>> soon somebody dares to mention an option name...
>>
>> Definitely more than it should, because it's gonna happen *every* time.
>>
>> https://en.wikipedia.org/wiki/Law_of_triviality
> 
> Doesn't mean it should not be frowned upon.

Or made light of, hence my post.  Personally I don't care what the
option is called, as long as we have docs for it.

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).

-- 
--
Josh Berkus
Red Hat OSAS
(any opinions are my own)


-- 
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: <572D0983.6030109@agliodbs.com>
Permalink:  ../572D0983.6030109@agliodbs.com/
Also on:    postgresql.org/message-id/572D0983.6030109@agliodbs.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: josh@agliodbs.com, andres@anarazel.de, jd@commandprompt.com, robertmhaas@gmail.com, sawada.mshk@gmail.com
  Subject: Re: Reviewing freeze map code
  In-Reply-To: <572D0983.6030109@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