Horton

Re: Doesn't pgstat_report_wal() handle the argument "force" incorrectly

Ryoga Yoshida <bt23yoshidar@oss.nttdata.com>

View thread View on postgr.es
From: Ryoga Yoshida <bt23yoshidar@oss.nttdata.com>
To: Michael Paquier <michael@paquier.xyz>
Cc: pgsql-hackers@lists.postgresql.org
Date: 2023-09-25T05:16:22Z
Lists: pgsql-hackers 
On 2023-09-25 12:47, Michael Paquier wrote:
in attached file
> +	/* like in pgstat.c, don't wait for lock acquisition when !force */

Isn't it the case with force=true and !force that it doesn't wait for 
the lock acquisition.  In fact, force may be false.

Ryoga Yoshida

Commits

  1. Fix behavior of "force" in pgstat_report_wal()