Re: More thoughts about planner's cost estimates - Mailing list pgsql-hackers

From Hannu Krosing
Subject Re: More thoughts about planner's cost estimates
Date
Msg-id 1149360367.3889.8.camel@localhost.localdomain
Whole thread Raw
In response to Re: More thoughts about planner's cost estimates  (Jim Nasby <jnasby@pervasive.com>)
Responses Re: More thoughts about planner's cost estimates  (Greg Stark <gsstark@mit.edu>)
List pgsql-hackers
Ühel kenal päeval, L, 2006-06-03 kell 10:43, kirjutas Jim Nasby:

> Might also be worth adding analyze delay settings, ala  
> vacuum_cost_delay.

Actually we should have delay settings for all potential
(almost-)full-scan service ops, - VACUUM, ANALYSE, CREATE INDEX, ADD
CONSTRAINT, maybe more - so that there would be better chances of
running those on busy databases without disastrous effects.

Probably we should use the same settings for all these, not invent a new
set for each.

-- 
----------------
Hannu Krosing
Database Architect
Skype Technologies OÜ
Akadeemia tee 21 F, Tallinn, 12618, Estonia

Skype me:  callto:hkrosing
Get Skype for free:  http://www.skype.com




pgsql-hackers by date:

Previous
From: Andrew Dunstan
Date:
Subject: Re: COPY (query) TO file
Next
From: Greg Stark
Date:
Subject: Re: COPY (query) TO file