Skip site navigation (1) Skip section navigation (2)

Re: More thoughts about planner's cost estimates

From: Hannu Krosing <hannu(at)skype(dot)net>
To: Jim Nasby <jnasby(at)pervasive(dot)com>
Cc: "Todd A(dot)Cook" <tcook(at)blackducksoftware(dot)com>,pgsql-hackers(at)postgresql(dot)org
Subject: Re: More thoughts about planner's cost estimates
Date: 2006-06-03 18:46:07
Message-ID: 1149360367.3889.8.camel@localhost.localdomain (view raw, whole thread or download thread mbox)
Lists: 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:

In response to


pgsql-hackers by date

Next:From: Nicolai PetriDate: 2006-06-03 19:05:02
Subject: Re: Faster Updates
Previous:From: Joachim WielandDate: 2006-06-03 18:23:53
Subject: Re: Allow commenting of variables in postgresql.conf to - try3

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group