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

From: Ryoga Yoshida <bt23yoshidar(at)oss(dot)nttdata(dot)com>
To: Michael Paquier <michael(at)paquier(dot)xyz>
Cc: pgsql-hackers(at)lists(dot)postgresql(dot)org
Subject: Re: Doesn't pgstat_report_wal() handle the argument "force" incorrectly
Date: 2023-09-25 05:16:22
Message-ID: 5adaf4e34fca5612ff506b47f6e81e47@oss.nttdata.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tatsuo Ishii 2023-09-25 05:26:30 Re: Row pattern recognition
Previous Message jian he 2023-09-25 04:52:40 Re: SQL:2011 application time