Re: [PERFORM] Very poor read performance, query independent - Mailing list pgsql-performance

From Igor Neyman
Subject Re: [PERFORM] Very poor read performance, query independent
Date
Msg-id DM5PR07MB28107393513C0A3B8C50F26BDAAE0@DM5PR07MB2810.namprd07.prod.outlook.com
Whole thread Raw
In response to Re: [PERFORM] Very poor read performance, query independent  (Charles Nadeau <charles.nadeau@gmail.com>)
List pgsql-performance

 

From: Charles Nadeau [mailto:charles.nadeau@gmail.com]
Sent: Tuesday, July 11, 2017 11:25 AM
To: Igor Neyman <ineyman@perceptron.com>
Cc: pgsql-performance@postgresql.org
Subject: Re: [PERFORM] Very poor read performance, query independent

 

Attention: This email was sent from someone outside of Perceptron. Always exercise caution when opening attachments or clicking links from unknown senders or when receiving unexpected emails.

 

Igor,

 

The sum of effective_cache_size and shared_buffer will be higher than the physical memory I have. Is it OK?

Thanks!

 

Charles

 

Yes, that’s normal.

 

shared_buffers is the maximum that Postgres allowed to allocate, while effective_cache_size is just a number that optimizer takes into account when creating execution plan.

 

Igor

 

pgsql-performance by date:

Previous
From: Charles Nadeau
Date:
Subject: Re: [PERFORM] Very poor read performance, query independent
Next
From: rverghese
Date:
Subject: Re: [PERFORM] vacuum analyze affecting query performance