From: | Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> |
---|---|
To: | Jelte Fennema-Nio <postgres(at)jeltef(dot)nl> |
Cc: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Create syscaches for pg_extension |
Date: | 2024-08-13 14:22:20 |
Message-ID: | CAFj8pRB6UES3yPH8mfvPnt=uknNcR9JdnLXcu2QW4C3bTezgDg@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
út 13. 8. 2024 v 16:13 odesílatel Jelte Fennema-Nio <postgres(at)jeltef(dot)nl>
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
Pavel
From | Date | Subject | |
---|---|---|---|
Next Message | Sofia Kopikova | 2024-08-13 14:38:42 | Apply PGDLLIMPORT markings to some GUC variables |
Previous Message | Greg Sabino Mullane | 2024-08-13 14:14:47 | Re: Subscription to Postgres Releases via ICS |