On 28 Únor 2012, 14:08, Claudio Freire wrote:
> On Tue, Feb 28, 2012 at 5:30 AM, Stefan Keller <sfkeller(at)gmail(dot)com> wrote:
>> But what I'm finally after is a solution, where records don't get
>> pushed back to disk a.s.a.p. but rather got hold in memory as long as
>> possible assuming that there is enough memory.
> fsync = off ?
I don't think this is a viable idea, unless you don't care about the data.
Moreover, "fsyn=off" does not mean "not writing" and writing does not mean
"removing from shared buffers". A page written/fsynced during a checkpoint
may stay in shared buffers.
AFAIK the pages are not removed from shared buffers without a reason. So a
dirty buffer is written to a disk (because it needs to, to keep ACID) but
stays in shared buffers as "clean" (unless it was written by a backend,
which means there's not enough memory).
In response to
pgsql-performance by date
|Next:||From: Claudio Freire||Date: 2012-02-28 13:52:28|
|Subject: Re: [PERFORM] Re: [PERFORM] Re: 回复： [PERFORM] ?==?UTF-8?Q?PG as in-memory db? How to warm up and re-populate buffers? ?==?UTF-8?Q?How to read in all tuples into memory?|
|Previous:||From: Claudio Freire||Date: 2012-02-28 13:08:25|
|Subject: Re: [PERFORM] Re: 回复： [PERFORM] PG as in-memor?==?UTF-8?Q?y db? How to warm up and re-populate buffers? How to read in?==?UTF-8?Q? all tuples into memory?|