[pgpool-hackers: 3520] Re: [pgpool-committers: 6594] pgpool: Fix last status changed timestamp is not set.

[Tatsuo Ishii]

I have noticed a nasty bug with the last status changed field in
pcp_node_info etc.  The reason why we did not notice the bug was that
the field is updated once a client connect to Pgpool-II.

Best regards,
--
Tatsuo Ishii
SRA OSS, Inc. Japan
English: http://www.sraoss.co.jp/index_en.php
Japanese:http://www.sraoss.co.jp

From: Tatsuo Ishii <ishii at sraoss.co.jp>
Subject: [pgpool-committers: 6594] pgpool: Fix last status changed timestamp is not set.
Date: Wed, 26 Feb 2020 01:43:44 +0000
Message-ID: <E1j6ljk-0001F5-38 at gothos.postgresql.org>

> Fix last status changed timestamp is not set.
> 
> If there's no status file or -D is specified when starting up
> Pgpool-II, the last status changed timestamp was not set and
> pcp_node_info command for example did not show the proper timestamp,
> rather showed 1970/1/1, which is the Unix timestamp epoch.
> 
> Note that correct timestamp is set once clients connect to Pgpool-II
> because at that time the status is changed from "waiting" to "up". So
> the phenomena is only observed before any client connects to the
> server.
> 
> Branch
> ------
> master
> 
> Details
> -------
> https://git.postgresql.org/gitweb?p=pgpool2.git;a=commitdiff;h=d15a4caeb8c65100251023c4ad3b229aef2b5f94
> 
> Modified Files
> --------------
> src/main/pgpool_main.c | 11 ++++++++++-
> 1 file changed, 10 insertions(+), 1 deletion(-)
>