Re: Avoid double lookup in pgstat_fetch_stat_tabentry() - Mailing list pgsql-hackers

From Drouvot, Bertrand
Subject Re: Avoid double lookup in pgstat_fetch_stat_tabentry()
Date
Msg-id 2e4a0ae1-2696-9f0c-301c-2330e447133f@gmail.com
Whole thread Raw
In response to Re: Avoid double lookup in pgstat_fetch_stat_tabentry()  (Bharath Rupireddy <bharath.rupireddyforpostgres@gmail.com>)
Responses Re: Avoid double lookup in pgstat_fetch_stat_tabentry()
Re: Avoid double lookup in pgstat_fetch_stat_tabentry()
List pgsql-hackers
Hi,

On 11/18/22 7:06 AM, Bharath Rupireddy wrote:
> On Fri, Nov 18, 2022 at 10:32 AM Drouvot, Bertrand
> <bertranddrouvot.pg@gmail.com> wrote:
>>
>> Hi hackers,
>>
>> Please find attached a patch proposal to avoid 2 calls to
>> pgstat_fetch_stat_tabentry_ext() in pgstat_fetch_stat_tabentry() in case
>> the relation is not a shared one and no statistics are found.
>>
>> Thanks Andres for the suggestion done in [1].
>>
>> [1]:
>> https://www.postgresql.org/message-id/20221116201202.3k74ajawyom2c3eq%40awork3.anarazel.de
> 
> +1. The patch LGTM. 

Thanks for looking at it!

> However, I have a suggestion to simplify it
> further by getting rid of the local variable tabentry and just
> returning pgstat_fetch_stat_tabentry_ext(IsSharedRelation(relid),
> relid);. Furthermore, the pgstat_fetch_stat_tabentry() can just be a
> static inline function.
Good point. While at it, why not completely get rid of 
pgstat_fetch_stat_tabentry_ext(), like in v2 the attached?

Regards,

-- 
Bertrand Drouvot
PostgreSQL Contributors Team
RDS Open Source Databases
Amazon Web Services: https://aws.amazon.com
Attachment

pgsql-hackers by date:

Previous
From: Pavel Stehule
Date:
Subject: Re: Patch: Global Unique Index
Next
From: Bharath Rupireddy
Date:
Subject: Re: when the startup process doesn't (logging startup delays)