Re: turn fastgetattr and heap_getattr to inline functions - Mailing list pgsql-hackers

From Japin Li
Subject Re: turn fastgetattr and heap_getattr to inline functions
Date
Msg-id MEYP282MB166906F3D37991C5B6095AC7B61A9@MEYP282MB1669.AUSP282.PROD.OUTLOOK.COM
Whole thread Raw
In response to Re: turn fastgetattr and heap_getattr to inline functions  (Japin Li <japinli@hotmail.com>)
List pgsql-hackers
On Fri, 25 Mar 2022 at 17:42, Alvaro Herrera <alvherre@alvh.no-ip.org> wrote:
> On 2022-Mar-24, Japin Li wrote:
>
>> Thanks for your detail explaination.  I find bottomup_sort_and_shrink_cmp()
>> has smilar code
>
> ... except that bottomup_sort_and_shrink_cmp never handles the case of
> the two structs being exactly identical, so I don't think this is a
> great counter-example.
>
>> IIUC, the last statement is used to keep the compiler quiet.  However,
>> it doesn't exist in LWLockAttemptLock().  Why?
>
> What I do care about is the fact that LWLockAttemptLock does compile
> silently everywhere without a final "return dummy_value" statement.

I'm just a bit confused about this.

> I
> don't have to build a theory for why the other function has a statement
> that may or may not be actually doing anything.

Anyway, thanks for your explaination!

--
Regrads,
Japin Li.
ChengDu WenWu Information Technology Co.,Ltd.



pgsql-hackers by date:

Previous
From: Pavel Borisov
Date:
Subject: Re: Fix unsigned output for signed values in SLRU error reporting
Next
From: Michael Paquier
Date:
Subject: Re: Allow file inclusion in pg_hba and pg_ident files