Re: Allow an extention to be updated without a script

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Yugo NAGATA <nagata(at)sraoss(dot)co(dot)jp>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: Allow an extention to be updated without a script
Date: 2023-01-30 21:05:52
Views: Raw Message | Whole Thread | Download mbox | Resend email
Lists: pgsql-hackers

Yugo NAGATA <nagata(at)sraoss(dot)co(dot)jp> writes:
> Currently, even when we don't need to execute any command to update an
> extension from one version to the next, we need to provide an update
> script that doesn't contain any command. Preparing such meaningless
> files are sometimes annoying.

If you have no update script, why call it a new version? The point
of extension versions is to distinguish different states of the
extension's SQL objects. We do not consider mods in underlying C code
to justify a new version.

> The attached patch introduces a new option "updates_without_script"
> into extension control file. This specifies a list of such updates
> following the pattern 'old_version--target_version'.

This seems completely unnecessary and confusing.

regards, tom lane

In response to


Browse pgsql-hackers by date

  From Date Subject
Next Message Jacob Champion 2023-01-30 21:12:31 Re: postgres_fdw, dblink, and CREATE SUBSCRIPTION security
Previous Message Jacob Champion 2023-01-30 21:02:04 Re: Authentication fails for md5 connections if ~/.postgresql/postgresql.{crt and key} exist