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

Re: More thoughts about planner's cost estimates

From: Greg Stark <gsstark(at)mit(dot)edu>
To: Hannu Krosing <hannu(at)skype(dot)net>
Cc: Jim Nasby <jnasby(at)pervasive(dot)com>, "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-04 21:34:47
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-hackers
Hannu Krosing <hannu(at)skype(dot)net> writes:

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

What about UPDATE and DELETE and for that matter SELECT?


In response to


pgsql-hackers by date

Next:From: Greg StarkDate: 2006-06-04 21:39:17
Subject: Re: Possible TODO item: copy to/from pipe
Previous:From: Magnus HaganderDate: 2006-06-04 19:17:40
Subject: Re: 'CVS-Unknown' buildfarm failures?

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