Re: Hardening pg_upgrade - Mailing list pgsql-hackers

From Magnus Hagander
Subject Re: Hardening pg_upgrade
Date
Msg-id CABUevEzy1NeawMKB00_3oBAAM6eTEQ_7YwYBUiV24Bjh+z2nWw@mail.gmail.com
Whole thread Raw
In response to Re: Hardening pg_upgrade  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Hardening pg_upgrade
List pgsql-hackers
On Thu, Aug 21, 2014 at 10:07 PM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
> Bruce Momjian <bruce@momjian.us> writes:
>> I tried writing the
>> query to use CTEs (second patch), but I would then have to have one
>> query for 8.3, which doesn't support CTEs, and another for 8.4+, plus
>> the CTE query was more complex than I liked.  Another idea would be to
>> drop 8.3 support (and remove lots of code to support that), but the
>> recent large increase in the number of people upgrading from 8.4 makes
>> that unattractive.  (8.3 did use a different timestamp storage format
>> though.)
>
> 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.


-- Magnus HaganderMe: http://www.hagander.net/Work: http://www.redpill-linpro.com/



pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Hardening pg_upgrade
Next
From: Peter Eisentraut
Date:
Subject: Re: run xmllint during build (was Re: need xmllint on borka)