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
Date: Mon, 30 Jan 2023 16:05:52 -0500
Message-ID: <888061.1675112752@sss.pgh.pa.us> (raw)
In-Reply-To: <20230131052502.0f5a522832cb26b631f44459@sraoss.co.jp>
References: <20230131052502.0f5a522832cb26b631f44459@sraoss.co.jp>
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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-hackers@postgresql.org
Cc: tgl@sss.pgh.pa.us, nagata@sraoss.co.jp
Subject: Re: Allow an extention to be updated without a script
In-Reply-To: <888061.1675112752@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox