Re: repeat() function, CHECK_FOR_INTERRUPTS(), and unlikely() - Mailing list pgsql-hackers

From Michael Paquier
Subject Re: repeat() function, CHECK_FOR_INTERRUPTS(), and unlikely()
Date
Msg-id 20200527072927.GE103662@paquier.xyz
Whole thread Raw
In response to Re: repeat() function, CHECK_FOR_INTERRUPTS(), and unlikely()  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: repeat() function, CHECK_FOR_INTERRUPTS(), and unlikely()
List pgsql-hackers
On Mon, May 25, 2020 at 11:14:39AM -0400, Tom Lane wrote:
> Perhaps I'm an optimist, but I think that eventually we will figure out
> how to make unlikely() work for MSVC.  In the meantime we might as well
> let it work for gcc-on-Windows builds.

I am less optimistic than that, but there is hope.  This was mentioned
as something considered for implementation in April 2019:
https://developercommunity.visualstudio.com/idea/488669/please-add-likelyunlikely-builtins.html

> I think that each of those tests should have a separate unlikely() marker,
> since the whole point here is that we don't expect either of those tests
> to yield true in the huge majority of CHECK_FOR_INTERRUPTS executions.

+1.  I am not sure that the addition of unlikely() should be
backpatched though, that's not something usually done.
--
Michael

Attachment

pgsql-hackers by date:

Previous
From: Amit Langote
Date:
Subject: Re: Getting ERROR with FOR UPDATE/SHARE for partitioned table.
Next
From: Michael Paquier
Date:
Subject: Re: max_slot_wal_keep_size comment in postgresql.conf