Re: [bug fix] Stats collector is not restarted on the standby

From: Michael Paquier <michael(dot)paquier(at)gmail(dot)com>
To: "Tsunakawa, Takayuki" <tsunakawa(dot)takay(at)jp(dot)fujitsu(dot)com>
Cc: "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: [bug fix] Stats collector is not restarted on the standby
Date: 2016-10-26 06:40:51
Message-ID: CAB7nPqRpjoQ=2xqGXd=YAgKMSx3v46qRT=hf5GMNLygK6UBzuQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Wed, Oct 26, 2016 at 2:46 PM, Tsunakawa, Takayuki
<tsunakawa(dot)takay(at)jp(dot)fujitsu(dot)com> wrote:
> If the stats collector is forcibly terminated on the standby in streaming replication configuration, it won't be restarted until the standby is promoted to the primary. The attached patch restarts the stats collector on the standby.
>
> FYI, when the stats collector is down, SELECTs against the statistics views get stale data with the following message.
>
> LOG: using stale statistics instead of current ones because stats collector is not responding
> STATEMENT: select * from pg_stat_user_tables

Oops. This could be a problem for some applications... As far as I can
see and after playing with it, your patch looks correct.
--
Michael

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Daniel Gustafsson 2016-10-26 06:52:19 Small typo in pageinspect heapfuncs
Previous Message Andres Freund 2016-10-26 06:31:39 Re: Proposal: scan key push down to heap [WIP]