From: Tom Lane <tgl@sss.pgh.pa.us>
To: Yugo NAGATA <nagata@sraoss.co.jp>
cc: pgsql-hackers@postgresql.org
Subject: Re: Allow an extention to be updated without a script
In-reply-to: <20230131052502.0f5a522832cb26b631f44459@sraoss.co.jp>
References: <20230131052502.0f5a522832cb26b631f44459@sraoss.co.jp>
Comments: In-reply-to Yugo NAGATA <nagata@sraoss.co.jp>
	message dated "Tue, 31 Jan 2023 05:25:02 +0900"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <888060.1675112752.1@sss.pgh.pa.us>
Date: Mon, 30 Jan 2023 16:05:52 -0500
Message-ID: <888061.1675112752@sss.pgh.pa.us>
Archived-At: 
 <https://www.postgresql.org/message-id/888061.1675112752%40sss.pgh.pa.us>
Precedence: bulk

Yugo NAGATA <nagata@sraoss.co.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