Re: SIGUSR1 pingpong between master na autovacum launcher causes crash - Mailing list pgsql-hackers

From Tom Lane
Subject Re: SIGUSR1 pingpong between master na autovacum launcher causes crash
Date
Msg-id 8502.1250949382@sss.pgh.pa.us
Whole thread Raw
In response to Re: SIGUSR1 pingpong between master na autovacum launcher causes crash  (Zdenek Kotala <Zdenek.Kotala@Sun.COM>)
Responses Re: SIGUSR1 pingpong between master na autovacum launcher causes crash  (Zdenek Kotala <Zdenek.Kotala@Sun.COM>)
List pgsql-hackers
Zdenek Kotala <Zdenek.Kotala@Sun.COM> writes:
> There are most important records from yesterdays issues. 
> Messages:
> ---------
> Aug 20 11:14:54 genunix: [ID 470503 kern.warning] WARNING: Sorry, no swap space to grow stack for pid 507 (postgres)

Hmm, that seems to confirm the idea that something had run the machine
out of memory/swap space, which would explain the repeated ENOMEM fork
failures.  But we're still no closer to understanding how come the
delay in the avlauncher didn't do what it was supposed to.
        regards, tom lane


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Lazy Snapshots
Next
From: Tom Lane
Date:
Subject: Re: [PATCH] plpythonu datatype conversion improvements