Re: Autovacuum vs statement_timeout - Mailing list pgsql-hackers

From Tom Lane
Subject Re: Autovacuum vs statement_timeout
Date
Msg-id 21578.1175276345@sss.pgh.pa.us
Whole thread Raw
In response to Re: Autovacuum vs statement_timeout  (Alvaro Herrera <alvherre@commandprompt.com>)
List pgsql-hackers
Alvaro Herrera <alvherre@commandprompt.com> writes:
> Hmmm, remember that DatabaseCancelAutovacuumActivity is called on CREATE
> DATABASE; but what it does is send SIGINT, not SIGTERM.  Also, it's not
> in 8.2.  SIGINT does terminate the autovac process however.
> I haven't read the whole problem report completely, so I'm not sure this
> has something to do or not.

AFAICT, SIGINT should be okay, because it will lead to an ERROR not a
FATAL elog; so control should fall out through the CATCH block before
the autovacuum process quits.  The problem is with FATAL elogs.

Mark reports that the only FATAL lines in his logs are instances ofFATAL:  terminating connection due to administrator
commandFATAL: database "launchpad_ftest" does not exist
 
and the latter presumably isn't coming out from within the btree vacuum
code, so I don't see any other explanation for a FATAL exit than SIGTERM.
        regards, tom lane


pgsql-hackers by date:

Previous
From: "Pavan Deolasee"
Date:
Subject: Re: CREATE INDEX and HOT - revised design
Next
From: Tom Lane
Date:
Subject: Re: Proposal: include PL/Proxy into core