Re: SQL function to access to `creating_extension`

From: Andrei Lepikhov <lepihov(at)gmail(dot)com>
To: Yurii Rashkovskii <yrashk(at)omnigres(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: SQL function to access to `creating_extension`
Date: 2025-08-01 14:33:17
Message-ID: edc6c0ee-0751-48cc-a798-d7b2fdcc9930@gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 19/4/2025 03:18, Yurii Rashkovskii wrote:
> This would allow for a generalized exclusion in pg_extension_config_dump.
>
> I've attached a draft patch for this simple function. I am happy to
> finalize it with tests and documentation if there is a consensus on the
> shape.
I must admit that I rarely use the pg_extension_config_dump feature.
Additionally, the term 'secondary extension' is not entirely clear to me.

To ensure we are on the same page, it would be helpful to see the
specific case you are referring to as a regression test or TAP test
included with the patch.

--
regards, Andrei Lepikhov

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Tender Wang 2025-08-01 14:45:20 Re: A little cosmetic to convert_VALUES_to_ANY()
Previous Message Tom Lane 2025-08-01 14:27:04 Re: C11 / VS 2019