Thread: BUG #4892: postmaster died and didn't restart

BUG #4892: postmaster died and didn't restart

From
"Rikard Pavelic"
Date:
The following bug has been logged online:

Bug reference:      4892
Logged by:          Rikard Pavelic
Email address:      rikard.pavelic@zg.htnet.hr
PostgreSQL version: 8.4 beta2
Operating system:   Windows XP SP3
Description:        postmaster died and didn't restart
Details:

log of death [i hate automatic translation feature :(]
%t LOG:  serverski proces (PID 5008) was terminated by exception 0xC0000142
%t HINT:  See C include file "ntstatus.h" for a description of the
hexadecimal value.
%t LOG:  terminiranje svih ostalih aktivnih serverskih procesa
%t WARNING:  terminating connection because of crash of another server
process
%t DETAIL:  The postmaster has commanded this server process to roll back
the current transaction and exit, because another server process exited
abnormally and possibly corrupted shared memory.
%t HINT:  In a moment you should be able to reconnect to the database and
repeat your command.
%t WARNING:  terminating connection because of crash of another server
process
%t DETAIL:  The postmaster has commanded this server process to roll back
the current transaction and exit, because another server process exited
abnormally and possibly corrupted shared memory.
%t HINT:  In a moment you should be able to reconnect to the database and
repeat your command.
%t LOG:  svi serverski procesi terminirani; reinicijalizacija
%t FATAL:  could not create shared memory segment: 1455
%t DETAIL:  Failed system call was CreateFileMapping(size=37044224,
name=Global/PostgreSQL:C:/Program Files/PostgreSQL/8.4/data).

and log after manual start
%t LOG:  database system was interrupted; last known up at 2009-06-25
23:41:15 CEST
%t FATAL:  rad baza podataka je u procesu startanja
%t LOG:  rad baze podataka nije bio ispravno prekinut; automatsko
oporavljanje u tijeku
%t LOG:  slog s nultom duljinom na 0/691A08
%t LOG:  redo nije tražen
%t LOG:  database system is ready to accept connections
%t LOG:  autovacuum launcher started

Re: BUG #4892: postmaster died and didn't restart

From
Tom Lane
Date:
"Rikard Pavelic" <rikard.pavelic@zg.htnet.hr> writes:
> %t FATAL:  could not create shared memory segment: 1455
> %t DETAIL:  Failed system call was CreateFileMapping(size=37044224,
> name=Global/PostgreSQL:C:/Program Files/PostgreSQL/8.4/data).

I know little about Windows, but according to Google code 1455 is
"ERROR_COMMITMENT_LIMIT: The paging file is too small for this operation
to complete".  Which seems to be an out-of-memory kind of problem.
Perhaps you've got shared_buffers set to an unreasonably high value
for your machine?

            regards, tom lane

Re: BUG #4892: postmaster died and didn't restart

From
Craig Ringer
Date:
On Sun, 2009-06-28 at 22:54 +0000, Rikard Pavelic wrote:

> log of death [i hate automatic translation feature :(]

On UNIX, it's so easy to change what language PostgreSQL uses that it's
generally considered very helpful - the only time you really want to
disable it is when posting to mailing lists.

On Windows, it might be nice to be able to set a language for Pg.

--
Craig Ringer

Re: BUG #4892: postmaster died and didn't restart

From
Alvaro Herrera
Date:
Craig Ringer wrote:
> On Sun, 2009-06-28 at 22:54 +0000, Rikard Pavelic wrote:
>
> > log of death [i hate automatic translation feature :(]
>
> On UNIX, it's so easy to change what language PostgreSQL uses that it's
> generally considered very helpful - the only time you really want to
> disable it is when posting to mailing lists.
>
> On Windows, it might be nice to be able to set a language for Pg.

Just set lc_messages in postgresql.conf.

--
Alvaro Herrera                                http://www.CommandPrompt.com/
The PostgreSQL Company - Command Prompt, Inc.