Excerpts from Robert Haas's message of jue sep 23 14:33:06 -0400 2010: > I'm worried about how we're going to manage that. First, as > pg_upgrade becomes more mature, the penalty for breaking on-disk > compatibility gets a LOT bigger. I'd like to think that "the next > time we break on-disk compatibility" means approximately "never", or > at least "not for a very long time". Second, if we do decide to break > it, how and when will we make that decision?
I liked your earlier suggestion: if somebody wants to pg_upgrade, he needs to go to the latest minor release of their branch, run some command to upgrade the on-disk format (say ALTER TABLE / SET TYPE), and *then* upgrade. Now if it was workable to handle floating-point datetimes to integer datetimes this way, it would be excellent. -- Álvaro Herrera <alvhe...@commandprompt.com> The PostgreSQL Company - Command Prompt, Inc. PostgreSQL Replication, Consulting, Custom Development, 24x7 support -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
