Re: DB page cache/query performance - Mailing list pgsql-general

From George Pavlov
Subject Re: DB page cache/query performance
Date
Msg-id 8C5B026B51B6854CBE88121DBF097A8602212D94@ehost010-33.exch010.intermedia.net
Whole thread Raw
In response to Re: DB page cache/query performance  (Greg Smith <gsmith@gregsmith.com>)
List pgsql-general
> From: Greg Smith [mailto:gsmith@gregsmith.com]
> Sent: Monday, May 19, 2008 9:03 PM
>
> So, yes, in 8.3 it's possible that you can have sequential
> scans of large
> tables or the VACUUM data pass through the buffer cache, but
> not remain in
> it afterwards.  I didn't think George would ever run into this in the
> specific example he asked about because of (1).  This
> behavior only kicks
> in if you're scanning a table large relative to the total
> shared buffer
> cache and that didn't seem like an issue in his case.

Correct -- the tables in this example were tiny, shared buffers are
large, and, in any case, I am still on 8.1...

George

pgsql-general by date:

Previous
From: Maarten Deprez
Date:
Subject: Re: escaping and quoting
Next
From: "Dan Joo"
Date:
Subject: Re: psql: FATAL: Ident authentication failed for user "postgres"