| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Eric Ridge <eebbrr(at)gmail(dot)com> |
| Cc: | Robert Haas <robertmhaas(at)gmail(dot)com>, Regina Obe <lr(at)pcorp(dot)us>, strk(at)kbt(dot)io, Regina Obe <r(at)pcorp(dot)us>, pgsql-hackers(at)lists(dot)postgresql(dot)org |
| Subject: | Re: [PATCH] Support % wildcard in extension upgrade filenames |
| Date: | 2023-05-01 20:24:30 |
| Message-ID: | 2297723.1682972670@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Eric Ridge <eebbrr(at)gmail(dot)com> writes:
> FWIW, outside of major ZDB releases, most of those have little-to-zero schema changes. But that doesn't negate the fact each release needs its own upgrade.sql script. I'm working on a point release right this moment and it won't have any schema changes but it'll have an upgrade.sql script.
Hmm ... our model for the in-core extensions has always been that you
don't need a new upgrade script unless the SQL declarations change.
Admittedly, that means that the script version number isn't a real
helpful guide to which version of the .so you're dealing with.
We expect the .so's own minor version number to suffice for that,
but I realize that that might not be the most user-friendly answer.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Eric Ridge | 2023-05-01 21:05:08 | Re: [PATCH] Support % wildcard in extension upgrade filenames |
| Previous Message | Peter Geoghegan | 2023-05-01 19:35:29 | Re: Overhauling "Routine Vacuuming" docs, particularly its handling of freezing |