On Thu, May 29, 2008 at 2:11 AM, Douglas McNaught [EMAIL PROTECTED] wrote:
On Wed, May 28, 2008 at 7:05 PM, Sabbiolina [EMAIL PROTECTED] wrote:
Hello, in my particular case I need to configure Postgres to handle only
a
few concurrent connections, but I need it to be blazingly fast, so I
On Thu, May 29, 2008 at 4:26 AM, Sabbiolina [EMAIL PROTECTED] wrote:
On Thu, May 29, 2008 at 2:11 AM, Douglas McNaught [EMAIL PROTECTED] wrote:
On Wed, May 28, 2008 at 7:05 PM, Sabbiolina [EMAIL PROTECTED] wrote:
Hello, in my particular case I need to configure Postgres to handle only
a
On Thu, May 29, 2008 at 01:05:22AM +0200, Sabbiolina wrote:
I have 4 Gigs of RAM, how do I force Postgres to use a higher part of such
memory in order to cache more indexes, queries and so on?
PG relies on the operating system to cache most disk accesses. Looking
at the amount of memory a
Sabbiolina wrote:
On Thu, May 29, 2008 at 2:11 AM, Douglas McNaught [EMAIL PROTECTED]
mailto:[EMAIL PROTECTED] wrote:
On Wed, May 28, 2008 at 7:05 PM, Sabbiolina [EMAIL PROTECTED]
mailto:[EMAIL PROTECTED] wrote:
Hello, in my particular case I need to configure Postgres to
On Thu, May 29, 2008 at 10:19:46AM -0400, Justin wrote:
To my understanding Postgresql only caches queries and results in memory
for that specific connection. So when that connection is closed those
cached results are cleared out.So cached indexs and queries are for
that connection
On Thu, May 29, 2008 at 10:19 AM, Justin [EMAIL PROTECTED] wrote:
To my understanding Postgresql only caches queries and results in memory for
that specific connection. So when that connection is closed those cached
results are cleared out.So cached indexs and queries are for that
Merlin Moncure wrote:
On Thu, May 29, 2008 at 10:19 AM, Justin [EMAIL PROTECTED] wrote:
To my understanding Postgresql only caches queries and results in memory for
that specific connection. So when that connection is closed those cached
results are cleared out.So cached indexs and
On Thu, May 29, 2008 at 4:45 PM, Justin [EMAIL PROTECTED] wrote:
Then what is the purpose of shared buffers if nothing is being reused is it
only used to keep track locks, changes and what is to being spooled to the
kernel???
It caches disk pages (and holds other data structures), not query
On Thu, 29 May 2008, Justin wrote:
I'm confussed trying to figure out how caches are being use and being
moving through postgresql backend.
The shared_buffers cache holds blocks from the database files. That's it.
If you want some more information about how that actually works head to
On Thu, May 29, 2008 at 4:52 PM, Dave Page [EMAIL PROTECTED] wrote:
On Thu, May 29, 2008 at 4:45 PM, Justin [EMAIL PROTECTED] wrote:
Then what is the purpose of shared buffers if nothing is being reused is it
only used to keep track locks, changes and what is to being spooled to the
On Thu, May 29, 2008 at 10:19 AM, Justin [EMAIL PROTECTED] wrote:
Quoting You Also, postgresql doesn't as a rule cache 'results and queries'.
Then what is the purpose of shared buffers if nothing is being reused is it
only used to keep track locks, changes and what is to being spooled to the
Hello, in my particular case I need to configure Postgres to handle only a
few concurrent connections, but I need it to be blazingly fast, so I need it
to cache everything possible. I've changed the config file and multiplied
all memory-related values by 10, still Postgres uses only less than 50
On Wed, May 28, 2008 at 7:05 PM, Sabbiolina [EMAIL PROTECTED] wrote:
Hello, in my particular case I need to configure Postgres to handle only a
few concurrent connections, but I need it to be blazingly fast, so I need it
to cache everything possible. I've changed the config file and multiplied
13 matches
Mail list logo
