Re: [INTERFACES] Slow join query optimisation?

On Thu, 2 Dec 1999, Tom Lane wrote:

> Date: Thu, 02 Dec 1999 10:21:43 -0500
> From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
> To: dougt(at)mugc(dot)cc(dot)monash(dot)edu(dot)au
> Cc: pgsql-interfaces(at)postgreSQL(dot)org
> Subject: Re: [INTERFACES] Slow join query optimisation?
>
> Douglas Thomson <dougt(at)mugc(dot)cc(dot)monash(dot)edu(dot)au> writes:
> > Is there any way to turn off the optimisation? Or perhaps some way to
> > work out the optimal strategy once, and then provide this information
> > directly?
>
> Not at the moment. There's been some talk of caching query plans,
> which would get the job done, but none of the current developers are
> working on that now. It'll probably happen someday...

What do you need to have 'someday' tomorrow :-?
Seriously, last topics about postgres performance indicate that
many people now seriously consider Postgres as a db engine for
real business application. And because business is more and more
shifting to Internet, we also need to think about Web-friendly
postgres features. One feature (LIMIT) implemented by Jan already
brings many Web-developers. Next was MVCC (and we're waiting for
WAL). We need DB pooling, which would be very useful in
high-performance Web application, CORBA interface is very important
(I currently just reading books). Caching query plans is very desirable,
probably not caching, but storing (naming), so developer could decide
which query should be stored.

Regards,

Oleg
>
> regards, tom lane
>
> ************
>

_____________________________________________________________
Oleg Bartunov, sci.researcher, hostmaster of AstroNet,
Sternberg Astronomical Institute, Moscow University (Russia)
Internet: oleg(at)sai(dot)msu(dot)su, http://www.sai.msu.su/~megera/
phone: +007(095)939-16-83, +007(095)939-23-83