Re: Wait event that should be reported while waiting for WALarchiving to finish - Mailing list pgsql-hackers

From Robert Haas
Subject Re: Wait event that should be reported while waiting for WALarchiving to finish
Date
Msg-id CA+Tgmoa3BVNJ+LVrytUrsK+MtxEogc_jurDgJ=rkMAEt06Hk6Q@mail.gmail.com
Whole thread Raw
In response to Re: Wait event that should be reported while waiting for WALarchiving to finish  (Fujii Masao <masao.fujii@oss.nttdata.com>)
Responses Re: Wait event that should be reported while waiting for WALarchiving to finish
List pgsql-hackers
On Thu, Feb 13, 2020 at 10:47 PM Fujii Masao
<masao.fujii@oss.nttdata.com> wrote:
> Fixed. Thanks for the review!

I think it would be safer to just report the wait event during
pg_usleep(1000000L) rather than putting those calls around the whole
loop. It does not seem impossible that ereport() or
CHECK_FOR_INTERRUPTS() could do something that reports a wait event
internally.

-- 
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company



pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: [HACKERS] Moving relation extension locks out of heavyweight lock manager
Next
From: Tom Lane
Date:
Subject: Re: Fix compiler warnings on 64-bit Windows