On 11/02/2014 02:41 PM, Tom Lane wrote:
Andrew Dunstan <and...@dunslane.net> writes:
On 11/02/2014 11:53 AM, Tom Lane wrote:
Well, the OID compatibility issue could be dodged by saying that we can't
do a pg_upgrade (in-place upgrade) of a database containing MONEY
columns. In fact, we might be able to just reject databases containing
MONEY[] (array) columns, which seems like it might be only a minor hazard.
Either way, requiring a dump/reload for upgrade is surely a better answer
for users of the type than just summarily screwing them.
Well, OK, yes, if we're prepared to abandon pg_upgrade-ability.
Not following your point? Removing the type entirely would certainly
break pg_upgrade-ability as well.
I'm not entirely convinced that we should remove it.
cheers
andrew
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
