On Tue, Sep 20, 2016 at 2:20 AM, Tsunakawa, Takayuki
<tsunakawa.takay@jp.fujitsu.com> wrote:
> There's no apparent evidence to indicate the cause, but I could guess a few reasons. What do you think these are
correctand should fix PostgreSQL? (I think so)
I think that we shouldn't start changing things based on guesses about
what the problem is, even if they're fairly smart guesses. The thing
to do would be to construct a test rig, crash the server repeatedly,
and add debugging instrumentation to figure out where the time is
actually going.
I do think your theory about the stats collector might be worth
pursuing. It seems that the stats collector only responds to SIGQUIT,
ignoring SIGTERM. Making it do a clean shutdown on SIGTERM and a fast
exit on SIGQUIT seems possibly worthwhile.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company