Horton

Re: [GENERAL] pg_upgrade problem

Tom Lane <tgl@sss.pgh.pa.us>

View thread
From: Tom Lane <tgl@sss.pgh.pa.us>
To: depesz@depesz.com
Cc: Bruce Momjian <bruce@momjian.us>, PostgreSQL-development <pgsql-hackers@postgresql.org>
Date: 2011-09-06T20:36:35Z
Lists: pgsql-hackers

Commits

Same data as JSON: GET /api/v1/messages/:b64id/commits the thread's linked commits as JSON, with link sources. API reference →

  1. ltree support for multibyte encodings. Patch was made by

hubert depesz lubaczewski <depesz@depesz.com> writes:
> Worked a bit to get the ltree problem down to smallest possible, repeatable, situation.

I looked at this again and verified that indeed, commit
8eee65c996048848c20f6637c1d12b319a4ce244 introduced an incompatible
change into the on-disk format of ltree columns: it widened
ltree_level.len, which is one component of an ltree on disk.
So the crash is hardly surprising.  I think that the only thing
pg_upgrade could do about it is refuse to upgrade when ltree columns
are present in an 8.3 database.  I'm not sure though how you'd identify
contrib/ltree versus some random user-defined type named ltree.

			regards, tom lane