Postgres Pro
Downloads
Home   >   mailing lists

Re: Database block lifecycle - Mailing list pgsql-general

From Robin
Subject Re: Database block lifecycle
Date
Msg-id BLU436-SMTP1296CEB85E7050A6CFA9C52E2EB0@phx.gbl
Whole thread Raw
In response to Re: Database block lifecycle  (Jeff Janes <jeff.janes@gmail.com>)
List pgsql-general
Tree view

On 13/08/2014 17:23, Jeff Janes wrote:

On Wed, Aug 13, 2014 at 1:07 AM, pinker <pinker@onet.eu> wrote:
>>
>> btw. 512MB if we assume up to 600 connection is a reasonable value?
>>
>
>>Reasonable value for what?
>
> For normal server load.

512MB is being questioned as a reasonable value for what?  shared_buffers?  work_mem?  maintenance_work_mem?

Cheers,

Jeff

Generally speaking, folk imagine that DBMS performance is all about disk access - in reality chucking as much memory as possible at the server(s) is an optimal investment. analyse your queries and store time critical stuff in memory

R+C

pgsql-general by date:

Previous
From: Jeff Janes
Date:
Subject: Re: Database block lifecycle
Next
From: Patrick Dung
Date:
Subject: Trigger function cannot reference field name with capital letter