| From: | Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at> |
|---|---|
| To: | Maciej Jaros <egil(at)wp(dot)pl>, Christophe Pettus <xof(at)thebuild(dot)com> |
| Cc: | pgsql-bugs(at)lists(dot)postgresql(dot)org |
| Subject: | Re: BUG #19927: PostgreSQL 16: SQL dump adds experimental/incompatible options like \restrict |
| Date: | 2026-11-21 08:43:11 |
| Message-ID: | 40131a22425af206efa0c93b1c6ec2f4b1d86dcb.camel@cybertec.at |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
On Fri, 2026-11-20 at 20:56 +0100, Maciej Jaros wrote:
> Well if the minor versions have breaking changes then how am I supposed to upgrade
> without making a backup? You seem to saying contradicting things.
I think you got that wrong. Upgrading wouldn't be a problem, as the dump from
16.15 would work with 19.0 without any problems. It is *down*grading that is the
problem. Moreover, as has been mentioned, moving from 16.3 to 16.16 wouldn't
need a dump (and it would solve your problem).
I keep being amazed at people who expend more effort resisting the update to the
latest minor version than the effort of the actual update would be.
Yours,
Laurenz Albe
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Zsolt Parragi | 2026-11-21 09:22:38 | Re: pg_rewind and hint bits leads to visibility corruption |
| Previous Message | Raja Sai pranav | 2026-11-21 08:27:21 | Re: BUG #19917: nbtree skip scan leaks one copy of a pass-by-reference skip array element per rescan |