| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Karsten Hilbert <Karsten(dot)Hilbert(at)gmx(dot)net> |
| Cc: | pgsql-general(at)lists(dot)postgresql(dot)org |
| Subject: | Re: Safest pgupgrade jump distance |
| Date: | 2024-02-12 16:52:31 |
| Message-ID: | 2238636.1707756751@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Karsten Hilbert <Karsten(dot)Hilbert(at)gmx(dot)net> writes:
> Am Mon, Feb 12, 2024 at 09:31:50AM -0500 schrieb Ron Johnson:
>> https://www.postgresql.org/docs/16/pgupgrade.html
>> "pg_upgrade supports upgrades from 9.2.X and later to the current major
>> release of PostgreSQL, including snapshot and beta releases."
> Just to be sure: it should be stressed that the binaries of
> the later version (16 in OPs case) should be used to run the
> upgrade, right ?
Right. Another thing worth pointing out here is that with such
a large jump distance, you'd better test application compatibility
before making the change on your production database. There are
likely to be a few gotchas.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Greg Sabino Mullane | 2024-02-12 16:54:53 | Re: Safest pgupgrade jump distance |
| Previous Message | Greg Sabino Mullane | 2024-02-12 16:46:35 | Re: How should we design our tables and indexes |