Re: Create syscaches for pg_extension

From: Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>
To: Andrei Lepikhov <lepihov(at)gmail(dot)com>
Cc: Michael Paquier <michael(at)paquier(dot)xyz>, Jelte Fennema-Nio <postgres(at)jeltef(dot)nl>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>, Alexander Korotkov <aekorotkov(at)gmail(dot)com>
Subject: Re: Create syscaches for pg_extension
Date: 2024-09-05 13:43:30
Message-ID: CAFj8pRDo9uhkDj3er5P_mtdjNHkOhWa3Auans81eQuJm-+qiog@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

čt 5. 9. 2024 v 15:41 odesílatel Andrei Lepikhov <lepihov(at)gmail(dot)com> napsal:

> On 22/8/2024 03:49, Michael Paquier wrote:
> > On Mon, Aug 19, 2024 at 03:21:30PM +0900, Michael Paquier wrote:
> >> I won't hide that I've wanted that in the past..
> >
> > And I have bumped into a case where this has been helpful today, so
> > applied. Thanks!
> It had been my dream, too, for years. But the reason was the too-costly
> call of the get_extension_oid routine (no less than pgbench 2-3% of
> overhead when checked it in the planner hook).
> It seems that the get_extension_oid routine was not modified when the
> sys cache was introduced. What is the reason? It may be that this
> routine is redundant now, but if not, and we want to hold the API that
> extensions use, maybe we should rewrite it, too.
> See the attachment proposing changes.
>

+1

Pavel

> --
> regards, Andrei Lepikhov
>

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Paul A Jungwirth 2024-09-05 13:45:44 Re: SQL:2011 application time
Previous Message Ranier Vilela 2024-09-05 13:43:24 Re: Avoid possible dereference null pointer (src/bin/pg_dump/pg_dump.c)