Re: Error: "could not fork new process for connection: Cannot allocate memory"

From: Fernando Hevia <fhevia(at)gmail(dot)com>
To: frank picabia <fpicabia(at)gmail(dot)com>
Cc: Postgres <pgsql-admin(at)postgresql(dot)org>
Subject: Re: Error: "could not fork new process for connection: Cannot allocate memory"
Date: 2020-12-21 19:35:31
Message-ID: CAGYT1XTa-B=tzHoCBc2iO9_6vVTXXQtn-=dbiO-OMfzz1W8T1Q@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-admin

El lun, 21 de dic. de 2020 a la(s) 10:25, frank picabia (fpicabia(at)gmail(dot)com)
escribió:

>
> Here are settings as suggested in the wiki to run a query to
> display those changed from defaults:
>
> name | current_setting | source
> ------------------------------+-------------------+----------------------
> effective_cache_size | 4TB | configuration file
>
>
Probably unrelated to your error perse, but this setting doesn't seem sane
on a 64 GB box... unless you have lots of swap on some remarkably fast
storage.

Regards,
Fernando.

In response to

Browse pgsql-admin by date

  From Date Subject
Next Message frank picabia 2020-12-21 20:17:49 Re: Error: "could not fork new process for connection: Cannot allocate memory"
Previous Message Tom Lane 2020-12-21 15:27:18 Re: Error: "could not fork new process for connection: Cannot allocate memory"