James Coleman <jtc...@gmail.com> writes: > On Mon, Sep 21, 2020 at 11:36 AM Tom Lane <t...@sss.pgh.pa.us> wrote: >> The recommended way to deal with updates these days is to leave the >> original extension script as-is and just write update scripts >> (1.0--1.1, 1.1--1.2, etc). That way, application of the updates >> is tested automatically every time you do CREATE EXTENSION.
> Ah, so just don't add a new 1.2 file, etc. > That also implies not having more direct upgrade paths (e.g., 1.0--1.2)? Right. Once the accumulation of cruft starts to impact install time substantially, maybe you want to roll things up to a new base version. But at least with the contrib modules we've found that it's seldom worth the trouble. regards, tom lane