On Tue, Nov 16, 2010 at 2:49 PM, Peter Eisentraut <pete...@gmx.net> wrote: > On lör, 2010-11-13 at 19:16 -0500, Robert Haas wrote: >> 1. The first one (relpersistence-v1) is a mostly mechanical patch that >> replaces pg_class.relistemp (a Boolean) with pg_class.relpersistence >> (a character), so that we can support more than two values. BE SURE >> YOU INITDB, since the old catalog format will not work with this patch >> applied. > > Btw., I would recommend that even in-progress or proposed patches > include catversion updates, which helps communicate the message such as > yours in a more robust manner and also reduces the chance of forgetting > the catversion change in the final commit.
I thought we had a policy of NOT doing that, because of the merge conflicts thereby created. It's also hard to know what value to set it to; whatever you pick will certainly be obsolete by commit time. -- Robert Haas EnterpriseDB: http://www.enterprisedb.com The Enterprise PostgreSQL Company -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
