| From: | Jim Nasby <Jim(dot)Nasby(at)BlueTreble(dot)com> |
|---|---|
| To: | Steve Crawford <scrawford(at)pinpointresearch(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Robert Haas <robertmhaas(at)gmail(dot)com>, Greg Stark <stark(at)mit(dot)edu>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Is it time to kill support for very old servers? |
| Date: | 2016-10-10 02:45:18 |
| Message-ID: | c240f82c-c373-6e76-5705-4f4855494e18@BlueTreble.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 10/7/16 1:08 PM, Steve Crawford wrote:
> This is effectively a 5-year upgrade "grace period" *after* the EOL date
> of a given version which seems plenty generous.
IMHO we need to be careful here. It's not at all unusual to see servers
running versions that are *far* older than that. It's certainly
understandable that we're not actively supporting those versions any
more, but we also don't want people to effectively be stranded on them
because they can't even get the data out and back into a newer version.
So I think pg_dump at least should try to support as far back as we can
without jumping to lots of hoops in code. I think moving the limit to
8.0 is fine, but I'm not so comfortable with making that limit 9.1.
--
Jim Nasby, Data Architect, Blue Treble Consulting, Austin TX
Experts in Analytics, Data Architecture and PostgreSQL
Data in Trouble? Get it in Treble! http://BlueTreble.com
855-TREBLE2 (855-873-2532) mobile: 512-569-9461
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jim Nasby | 2016-10-10 02:51:17 | Re: Question / requests. |
| Previous Message | Jim Nasby | 2016-10-10 02:36:08 | Re: pg_dump getBlobs query broken for 7.3 servers |