| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
| Cc: | Wells Oliver <wells(dot)oliver(at)gmail(dot)com>, pgsql-admin <pgsql-admin(at)postgresql(dot)org> |
| Subject: | Re: Setting effective_cache_size in integer form with the 8kb block units |
| Date: | 2022-01-19 22:21:01 |
| Message-ID: | 770649.1642630861@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
"David G. Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> writes:
> On Wed, Jan 19, 2022 at 2:57 PM Wells Oliver <wells(dot)oliver(at)gmail(dot)com> wrote:
>> It does. In a cruel twist of fate, RDS parameter groups do not allow
>> "48GB" and want integer values.
> The system operates and calculates memory in binary per the referenced
> documentation so 6,291,456 (I double-checked this).
If you don't trust hand arithmetic, try
regression=# set effective_cache_size to '48GB';
SET
regression=# select setting from pg_settings where name = 'effective_cache_size';
setting
---------
6291456
(1 row)
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Wells Oliver | 2022-01-19 22:25:04 | Re: Setting effective_cache_size in integer form with the 8kb block units |
| Previous Message | David G. Johnston | 2022-01-19 22:15:06 | Re: Setting effective_cache_size in integer form with the 8kb block units |