| From: | Alan Hodgson <ahodgson(at)lists(dot)simkin(dot)ca> |
|---|---|
| To: | "pgsql-generallists(dot)postgresql(dot)org" <pgsql-general(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Memory footprint diff between 9.5 and 12 |
| Date: | 2020-05-07 22:03:48 |
| Message-ID: | 3ce4589dae05ec0f3308b0fb86f7a8a895e7b753.camel@lists.simkin.ca |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Thu, 2020-05-07 at 13:33 -0700, Tory M Blue wrote:
> I hadn't noticed this until today, but a running 9.5 system with
> buffers at 10GB starts and has been running years without issues.
> (15GB available)
> Postgres 12 will not start with that configuration, complaining about
> memory availability. So Postgres12 won't start until shared buffers
> is 6GB, but even with that, my DB servers , postgres queries started
> complaining about being unable to allocate memory "unable to
> allocate".
>
> So dropping them to 4GB (on a 15GB system), may help, but did I miss a
> huge note about significant memory changes between 9.5 to 12?
>
> Is there something else I'm missing that on busy systems is important,
> something introduced in 10 or 11 as again I'm not seeing anything
> noted in 12.
> Thanks
Is this running on an otherwise identical system? Or do you have a
different kernel, overcommit settings, or swap configuration?
| From | Date | Subject | |
|---|---|---|---|
| Next Message | David Rowley | 2020-05-07 23:46:00 | Re: Explain plan changes - IN CLAUSE ( Passing direct values Vs INNER Query ) |
| Previous Message | David G. Johnston | 2020-05-07 21:59:43 | Re: Explain plan changes - IN CLAUSE ( Passing direct values Vs INNER Query ) |