Re: Database block lifecycle - Mailing list pgsql-general

From pinker
Subject Re: Database block lifecycle
Date
Msg-id 1407917229708-5814672.post@n5.nabble.com
Whole thread Raw
In response to Re: Database block lifecycle  (Jeff Janes <jeff.janes@gmail.com>)
Responses Re: Database block lifecycle  (Jeff Janes <jeff.janes@gmail.com>)
List pgsql-general
Jeff Janes wrote
> On Tuesday, August 12, 2014, pinker <

> pinker@

> > wrote:
>
>> Do you ever plan on restarting this server?  Doing maintenance?  Applying
>> security patches?
>
> Sure, I assumed when db is up and running, of course after first read from
> disk when whole data should be in RAM.
>
>
>> More like b), but you are missing all the states that involve "clean in
>> shared_buffers, dirty in FS cache" and such.
>
> Ok, so modified block is taken from shared_buffers or from RAM when
> needed, and is readed always from shared buffers?
>
>
>>
>> btw. 512MB if we assume up to 600 connection is a reasonable value?
>>
>
>>Reasonable value for what?
>
> For normal server load.
>
> Cheers,
>
> Jeff





--
View this message in context: http://postgresql.1045698.n5.nabble.com/Database-block-lifecycle-tp5814627p5814672.html
Sent from the PostgreSQL - general mailing list archive at Nabble.com.


pgsql-general by date:

Previous
From: Seref Arikan
Date:
Subject: Re: PostgreSQL as a triple store
Next
From: Chris Travers
Date:
Subject: Re: PostgreSQL as a triple store