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

Re: caching table/query

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Tsirkin Evgeny <tsurkin(at)mail(dot)jct(dot)ac(dot)il>
Cc: Michael Fuhr <mike(at)fuhr(dot)org>, Tsirkin Evgeny <tsurkin(at)jct(dot)ac(dot)il>,pgsql-admin(at)postgresql(dot)org
Subject: Re: caching table/query
Date: 2005-07-17 15:53:27
Message-ID: 28088.1121615607@sss.pgh.pa.us (view raw or flat)
Thread:
Lists: pgsql-admin
Tsirkin Evgeny <tsurkin(at)mail(dot)jct(dot)ac(dot)il> writes:
> What i realy want is to say to postgres that the particular
> table should be cached .

Adopting the position that you are smarter than an automatic
optimization algorithm is generally a good way to achieve less
performance, not more.  Especially so if you are willing to override
the automatic algorithm on the strength of guesses that you make
when you haven't even seen the system in operation yet.  The truth
of the matter is that you haven't got the foggiest idea yet where
the system bottlenecks will be, and so you should certainly not be
thinking about how to override the cache manager.

If you've not heard the phrase "premature optimization is the root of
all evil", I suggest you read up on it.  It's generally good advice.

			regards, tom lane

In response to

Responses

pgsql-admin by date

Next:From: Magnus HaganderDate: 2005-07-17 20:40:28
Subject: Re: Install Problem on Windows XP Home - Password Issue
Previous:From: Tsirkin EvgenyDate: 2005-07-17 14:58:46
Subject: Re: caching table/query

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