Tsirkin Evgeny <tsurkin@xxxxxxxxxxxxxx> 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
