On Sun, May 27, 2012 at 12:08:14PM -0400, Bruce Momjian wrote: > > > We are not writing a one-off pg_upgrade for JSON-backpatchers here. > > > > I tend to agree with that position, and particularly think that we > > should not allow the not-community-approved design of the existing > > JSON backport to drive changes to pg_upgrade. It would be better to > > ask first if there were a different way to construct that backport > > that would fit better with pg_upgrade. > > Yep. > > A command-line flag just seems too user-visible for this use-case, and > too error-pone. I barely understand what is going on, particularly with > plpython in "public" (which we don't fully even understand yet), so > adding a command-line flag seems like the wrong direction.
FYI, I recommend to Andrew that he just set probin to NULL for the JSON type in the old cluster before performing the upgrade. -- Bruce Momjian <br...@momjian.us> http://momjian.us EnterpriseDB http://enterprisedb.com + It's impossible for everything to be true. + -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
