public inbox for [email protected]  
help / color / mirror / Atom feed
From: Alexander Korotkov <[email protected]>
To: Pavel Stehule <[email protected]>
Cc: Jelte Fennema-Nio <[email protected]>
Cc: PostgreSQL-development <[email protected]>
Subject: Re: Create syscaches for pg_extension
Date: Tue, 13 Aug 2024 17:38:55 +0300
Message-ID: <CAPpHfdsQnXcKZT2D7Evv-uuugcbToOri5fnoNcMiqLq9UtyWXQ@mail.gmail.com> (raw)
In-Reply-To: <CAFj8pRB6UES3yPH8mfvPnt=uknNcR9JdnLXcu2QW4C3bTezgDg@mail.gmail.com>
References: <CAGECzQTWm9sex719Hptbq4j56hBGUti7J9OWjeMobQ1ccRok9w@mail.gmail.com>
	<CAFj8pRB6UES3yPH8mfvPnt=uknNcR9JdnLXcu2QW4C3bTezgDg@mail.gmail.com>

On Tue, Aug 13, 2024 at 5:23 PM Pavel Stehule <[email protected]> wrote:
> út 13. 8. 2024 v 16:13 odesílatel Jelte Fennema-Nio <[email protected]> napsal:
>>
>> Shared libraries of extensions might want to invalidate or update their
>> own caches whenever a CREATE/ALTER/DROP EXTENSION command is run for
>> their extension (in any backend). Right now this is non-trivial to do
>> correctly and efficiently. But if the extension catalog was part of a
>> syscache this could simply be done by registering an callback using
>> CacheRegisterSyscacheCallback for the relevant syscache.
>>
>> This change is only made to make the lives of extension authors easier.
>> The performance impact of this change should be negligible, since
>> updates to pg_extension are very rare.
>
>
> +1

+1 from me too

------
Regards,
Alexander Korotkov
Supabase






view thread (2+ messages)

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: [email protected]
  Cc: [email protected], [email protected], [email protected]
  Subject: Re: Create syscaches for pg_extension
  In-Reply-To: <CAPpHfdsQnXcKZT2D7Evv-uuugcbToOri5fnoNcMiqLq9UtyWXQ@mail.gmail.com>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox