Re: Database block lifecycle

From: pinker <pinker(at)onet(dot)eu>
To: pgsql-general(at)postgresql(dot)org
Subject: Re: Database block lifecycle
Date: 2014-08-13 08:07:09
Message-ID: 1407917229708-5814672.post@n5.nabble.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Jeff Janes wrote
> On Tuesday, August 12, 2014, pinker &lt;

> pinker@

> &gt; 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.

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Chris Travers 2014-08-13 09:15:59 Re: PostgreSQL as a triple store
Previous Message Seref Arikan 2014-08-13 07:43:54 Re: PostgreSQL as a triple store