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

From: Sandro Santilli <strk(at)kbt(dot)io>
To: pgsql-hackers(at)lists(dot)postgresql(dot)org
Cc: Mat Arye <mat(at)timescaledb(dot)com>, Regina Obe <lr(at)pcorp(dot)us>, Yurii Rashkovskii <yrashk(at)gmail(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Regina Obe <r(at)pcorp(dot)us>
Subject: Re: [PATCH] Support % wildcard in extension upgrade filenames
Date: 2023-05-31 19:07:43
Message-ID: 20230531190743.nzktxombkupb25ud@c19
Views: Raw Message | Whole Thread | Download mbox | Resend email
Lists: pgsql-hackers

On Thu, Apr 27, 2023 at 12:49:57PM +0200, Sandro Santilli wrote:
> On Mon, Apr 24, 2023 at 01:06:24PM -0400, Mat Arye wrote:
> > Hi All,
> >
> > I've done upgrade maintenance for multiple extensions now (TimescaleDB
> > core, Promscale) and I think the original suggestion (wildcard filenames
> > with control-file switch to enable) here is a good one.
> Thanks for your comment, Mat.
> I'm happy to bring back the control-file switch if there's an
> agreement about that.

I'm attaching an up-to-date version of the patch with the control-file
switch back in, so there's an explicit choice by extension developers.


Attachment Content-Type Size
v3-0001-Allow-wildcard-in-extension-upgrade-paths.patch text/x-diff 10.3 KB

In response to


Browse pgsql-hackers by date

  From Date Subject
Next Message Laurenz Albe 2023-05-31 19:08:13 Re: Question - Does PostgreSQL have an Evaluation Assurance Level?
Previous Message Laurenz Albe 2023-05-31 19:03:33 Re: Support edit order of the fields in table