| From: | Igor Neyman <ineyman(at)perceptron(dot)com> |
|---|---|
| To: | Charles Nadeau <charles(dot)nadeau(at)gmail(dot)com> |
| Cc: | "pgsql-performance(at)postgresql(dot)org" <pgsql-performance(at)postgresql(dot)org> |
| Subject: | Re: Very poor read performance, query independent |
| Date: | 2017-07-11 15:46:30 |
| Message-ID: | DM5PR07MB28107393513C0A3B8C50F26BDAAE0@DM5PR07MB2810.namprd07.prod.outlook.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
From: Charles Nadeau [mailto:charles(dot)nadeau(at)gmail(dot)com]
Sent: Tuesday, July 11, 2017 11:25 AM
To: Igor Neyman <ineyman(at)perceptron(dot)com>
Cc: pgsql-performance(at)postgresql(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | rverghese | 2017-07-11 15:57:01 | Re: vacuum analyze affecting query performance |
| Previous Message | Charles Nadeau | 2017-07-11 15:25:14 | Re: Very poor read performance, query independent |