Re: amcheck (B-Tree integrity checking tool) - Mailing list pgsql-hackers

From Jim Nasby
Subject Re: amcheck (B-Tree integrity checking tool)
Date
Msg-id 56E3633A.7030507@BlueTreble.com
Whole thread Raw
In response to Re: amcheck (B-Tree integrity checking tool)  (Peter Geoghegan <pg@heroku.com>)
Responses Re: amcheck (B-Tree integrity checking tool)
List pgsql-hackers
On 3/11/16 6:17 PM, Peter Geoghegan wrote:
> Not sure about the cost delay thing. Delays are disabled by default
> for manually issued VACUUM, so have doubts that that's useful.

Right, but you still have the option to enable them if you don't want to 
swamp your IO system. That's why CIC obeys it too. If I was running a 
consistency check on a production system I'd certainly want the option 
to throttle it. Without that option, I don't see running this on 
production systems as being an option. If that's not a goal then fine, 
but if it is a goal I think it needs to be there.

Isn't it just a few extra lines of code to support it?
-- 
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



pgsql-hackers by date:

Previous
From: Peter Geoghegan
Date:
Subject: Re: amcheck (B-Tree integrity checking tool)
Next
From: Jim Nasby
Date:
Subject: Re: Is there a way around function search_path killing SQL function inlining? - and backup / restore issue