Loss of cache when persistent connexion is closed - Mailing list pgsql-performance

From Guillaume Pungeot
Subject Loss of cache when persistent connexion is closed
Date
Msg-id 95c13b360801080735y181e4f5fs75c0741603f6021c@mail.gmail.com
Whole thread Raw
Responses Re: Loss of cache when persistent connexion is closed
List pgsql-performance
Hello,
I have a problem with my install of postgresql. I have a program that requests DB by opening persistent connexions. When the program is launched, the disk IO are very high until postgresql cache is good enough (a few hours). The problem is that when I stop the program all the connexions are closed and so are the postrgesql processes. And the cache is lost.
I really want to use postgresql but today I use mssqlserver and it never lost its cache till I stop it (mssqlserver). So I don't have problem with disk IO when the program is stopped an restarted.

I assume that each postgresql process manage its own cache but that there is no global cache. Am I right ? If true is there any possibility to have a global cache for all processes and is it possible not to free this cache when connexions are closed ?

Regards

--
=========
Guillaume Pungeot - mappy

pgsql-performance by date:

Previous
From: Tom Lane
Date:
Subject: Re: Linux/PostgreSQL scalability issue - problem with 8 cores
Next
From: Tom Lane
Date:
Subject: Re: Loss of cache when persistent connexion is closed