RE: [PATCH] Support % wildcard in extension upgrade filenames

From: "Regina Obe" <lr(at)pcorp(dot)us>
To: "'Gregory Stark \(as CFM\)'" <stark(dot)cfm(at)gmail(dot)com>, "'Sandro Santilli'" <strk(at)kbt(dot)io>
Cc: "'Tom Lane'" <tgl(at)sss(dot)pgh(dot)pa(dot)us>, "'Regina Obe'" <r(at)pcorp(dot)us>, <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: RE: [PATCH] Support % wildcard in extension upgrade filenames
Date: 2023-03-06 21:37:39
Message-ID: 000901d95073$e0c5a290$a250e7b0$@pcorp.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

> This patch too is conflicting on meson.build. Are these two patches
> interdependent?
>
> This one looks a bit more controversial. I'm not sure if Tom has been
> convinced and I haven't seen anyone else speak up.
>
> Perhaps this needs a bit more discussion of other options to solve this issue.
> Maybe it can just be solved with multiple one-line scripts that call to a master
> script?
>
> --
> Gregory Stark
> As Commitfest Manager

They edit the same file yes so yes conflicts are expected.
The wildcard one, Tom was not convinced, so I assume we'll need to
go a couple more rounds on it and hopefully we can get something that will not be so controversial.

I don't think the schema qualifying required extension feature is controversial though so I think that should be able to go and we'll rebase our other patch after that.

Thanks,
Regina

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Regina Obe 2023-03-06 21:40:29 RE: Ability to reference other extensions by schema in extension scripts
Previous Message Daniel Gustafsson 2023-03-06 21:24:30 Re: On login trigger: take three