On Thu, Aug 21, 2014 at 10:07 PM, Tom Lane <t...@sss.pgh.pa.us> wrote: > Bruce Momjian <br...@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 Hagander Me: http://www.hagander.net/ Work: http://www.redpill-linpro.com/ -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
