| From: | Jim Nasby <Jim(dot)Nasby(at)BlueTreble(dot)com> |
|---|---|
| To: | Peter Geoghegan <pg(at)heroku(dot)com> |
| Cc: | Tomas Vondra <tomas(dot)vondra(at)2ndquadrant(dot)com>, Pg Hackers <pgsql-hackers(at)postgresql(dot)org>, Anastasia Lubennikova <a(dot)lubennikova(at)postgrespro(dot)ru> |
| Subject: | Re: amcheck (B-Tree integrity checking tool) |
| Date: | 2016-03-12 00:30:50 |
| Message-ID: | 56E3633A.7030507@BlueTreble.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | 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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jim Nasby | 2016-03-12 00:35:17 | Re: Is there a way around function search_path killing SQL function inlining? - and backup / restore issue |
| Previous Message | Peter Geoghegan | 2016-03-12 00:17:54 | Re: amcheck (B-Tree integrity checking tool) |