Re: BUG #14101: Postgres Service Crashes With Memory Error And Does Not Recover

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: nathanmascitelli(at)geotab(dot)com
Cc: pgsql-bugs(at)postgresql(dot)org
Subject: Re: BUG #14101: Postgres Service Crashes With Memory Error And Does Not Recover
Date: 2016-04-20 03:57:00
Message-ID: 25458.1461124620@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

nathanmascitelli(at)geotab(dot)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=00000000000000D0,
> addr=00000001405E0000): error code 1455

Hm, that's an odd one. According to
https://msdn.microsoft.com/en-us/library/windows/desktop/ms681385(v=vs.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

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Michael Paquier 2016-04-20 07:53:35 Re: Re: BUG #13685: Archiving while idle every archive_timeout with wal_level hot_standby
Previous Message Noah Misch 2016-04-20 02:28:56 Re: postmaster became multithreaded during startup