Re: performance while importing a very large data set in to database - Mailing list pgsql-performance

From Greg Smith
Subject Re: performance while importing a very large data set in to database
Date
Msg-id 4B1BCAA2.1010505@2ndquadrant.com
Whole thread Raw
In response to Re: performance while importing a very large data set in to database  (Kris Kewley <kris.kewley@gmail.com>)
List pgsql-performance
Kris Kewley wrote:
> Does postgres have the concept of "pinning" procs, functions, etc to
> cache.
>
No.  Everything that's in PostgreSQL's cache gets a usage count attached
to is.  When the buffer is used by something else, that count gets
incremented.  And when new buffers need to be allocated, the process
that searches for them decrements usage counts until it find one with a
count of 0 that's then evicted.  There's no way to pin things using this
scheme, the best you can do is try to access the data in advance and/or
regularly enough that its usage count never drops too far.

--
Greg Smith    2ndQuadrant   Baltimore, MD
PostgreSQL Training, Services and Support
greg@2ndQuadrant.com  www.2ndQuadrant.com


pgsql-performance by date:

Previous
From: Kris Kewley
Date:
Subject: Re: performance while importing a very large data set in to database
Next
From: Andres Freund
Date:
Subject: Re: Large DB, several tuning questions: Index sizes, VACUUM, REINDEX, Autovacuum