| From: | Michael Paquier <michael(at)paquier(dot)xyz> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>, Peter Eisentraut <peter(at)eisentraut(dot)org>, Matheus Alcantara <matheusssilv97(at)gmail(dot)com>, Pierrick <pierrick(dot)chovelon(at)dalibo(dot)com>, "pgsql-hackers(at)lists(dot)postgresql(dot)org" <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Only one version can be installed when using extension_control_path |
| Date: | 2025-09-10 23:38:44 |
| Message-ID: | aMIMBO46Mc1lZjDG@paquier.xyz |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Mon, Sep 08, 2025 at 11:35:42AM -0400, Tom Lane wrote:
> Between this and previously-identified problems (commits 81eaaa2c4,
> f777d7738), it seems clear that extension_control_path (which is a new
> thing in v18) was very poorly thought out. I wonder if it's too late
> to revert it so that we can redesign it more carefully.
It would be too late once we are in GA, and we are not yet in GA. At
this point I think that this should be Peter's call.
I am not in his shoes, still I suspect like you that we may have not
seen the end of it yet. If we're confident enough that we can fix
anything, that's fine as a response to me, but discussions are also
involving how available extensions are seen at catalog level. This
bit is concerning for me, but I'm also of a pessimistic nature.
--
Michael
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Michael Paquier | 2025-09-10 23:48:47 | Re: Stale comment in guc.h; publish listing of setting sources? |
| Previous Message | Masahiko Sawada | 2025-09-10 23:30:56 | Re: Proposal: Out-of-Order NOTIFY via GUC to Improve LISTEN/NOTIFY Throughput |