Postgres Pro
Downloads
Home   >   mailing lists

Re: Doesn't pgstat_report_wal() handle the argument "force" incorrectly - Mailing list pgsql-hackers

From Ryoga Yoshida
Subject Re: Doesn't pgstat_report_wal() handle the argument "force" incorrectly
Date
Msg-id 5adaf4e34fca5612ff506b47f6e81e47@oss.nttdata.com
Whole thread Raw
In response to Re: Doesn't pgstat_report_wal() handle the argument "force" incorrectly  (Michael Paquier <michael@paquier.xyz>)
Responses Re: Doesn't pgstat_report_wal() handle the argument "force" incorrectly
List pgsql-hackers
Tree view 
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

pgsql-hackers by date:

Previous
From: jian he
Date:
Subject: Re: SQL:2011 application time
Next
From: Tatsuo Ishii
Date:
Subject: Re: Row pattern recognition