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 9594.1250885892@sss.pgh.pa.us
Whole thread Raw
In response to Re: SIGUSR1 pingpong between master na autovacum launcher causes crash  (Alvaro Herrera <alvherre@commandprompt.com>)
Responses Re: SIGUSR1 pingpong between master na autovacum launcher causes crash  (Alvaro Herrera <alvherre@commandprompt.com>)
List pgsql-hackers
Alvaro Herrera <alvherre@commandprompt.com> writes:
> If sigusr1_handler needs rewriting, don't all the other sighandler as
> well?

It does not, and neither do they.  I'm not sure what happened here but
it wasn't the fault of the postmaster's organization of signal handlers.

It does seem that we ought to change things so that there's a bit more
delay before trying to re-launch a failed autovac worker, though.
Whatever caused this was effectively turning the autovac logic into
a fork-bomb engine.  I'm not thinking of just postponing the relaunch
into the main loop, but ensuring at least a few hundred msec delay before
we try again.
        regards, tom lane


pgsql-hackers by date:

Previous
From: Zdenek Kotala
Date:
Subject: Re: SIGUSR1 pingpong between master na autovacum launcher causes crash
Next
From: Tom Lane
Date:
Subject: Re: Feedback about Drupal SQL debugging