Hi Tom,=E2=80=8B
The machine has the postgres server and our application server on it. There
are =E2=80=8Baround 300 databases and typically ~1000 connections. At the t=
ime of
the crash there was free RAM and disk space on the server.
Is there any other information I can give you?
Thanks,
*Nathan Mascitelli*
Geotab Inc.
Software Developer | B. Eng Engineering Physics
[Direct] *+1 (289) 681-1005*
[Toll-Free] *+1 (877) 436-8221*
[Visit] www.geotab.com
Twitter <http://twitter.com/geotab> | Facebook
<http://www.facebook.com/geotab> | YouTube <http://www.youtube.com/mygeotab=
>
| LinkedIn
<http://www.linkedin.com/company/102661?trk=3Dtyah&trkInfo=3DtarId:14031992=
50031,tas:geotab,idx:2-1-3>
On Tue, Apr 19, 2016 at 11:57 PM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
> nathanmascitelli@geotab.com writes:
> > I am running Postgres 9.4 on Windows Server 2012. I have had postgres
> crash
> > a few times with the following error:
> > FATAL: could not reattach to shared memory (key=3D00000000000000D0=
,
> > addr=3D00000001405E0000): error code 1455
>
> Hm, that's an odd one. According to
>
> https://msdn.microsoft.com/en-us/library/windows/desktop/ms681385(v=3Dvs.=
85).aspx
> that is
>
> ERROR_COMMITMENT_LIMIT
> 1455 (0x5AF)
> The paging file is too small for this operation to complete.
>
> which suggests that this is a resource-exhaustion type of problem.
> How many backend processes are you trying to run concurrently,
> and what else is running on the machine?
>
> regards, tom lane
>
