| From: | Bernd Helmle <mailings(at)oopsware(dot)de> |
|---|---|
| To: | Magnus Hagander <magnus(at)hagander(dot)net>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Bruce Momjian <bruce(at)momjian(dot)us>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Hardening pg_upgrade |
| Date: | 2014-08-25 08:18:03 |
| Message-ID: | D30C7EE3805EB736C6EC6C01@eje.credativ.lan |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
--On 21. August 2014 22:08:58 +0200 Magnus Hagander <magnus(at)hagander(dot)net>
wrote:
>> I vote for discarding 8.3 support in pg_upgrade. There are already
>> enough limitations on pg_upgrade from pre-8.4 to make it of questionable
>> value; if it's going to create problems like this, it's time to cut the
>> rope.
>
> +1. 8.3 has been unsupported for a fairly long time now, and you can
> still do a two-step upgrade if you're on that old a version.
Also +1 from my side. I've seen some old 8.3 installations at customers,
still, but they aren't large and can easily be upgraded with a two step
upgrade.
--
Thanks
Bernd
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Heikki Linnakangas | 2014-08-25 09:37:14 | Re: Extended Prefetching using Asynchronous IO - proposal and patch |
| Previous Message | Sawada Masahiko | 2014-08-25 07:33:53 | Re: Concurrently option for reindexdb |