Bruce Momjian <[EMAIL PROTECTED]> writes:
I think we should fix it but not force an initdb --- information_schema is new and I am not sure how many people are using it.
Yeah, I'm leaning that way too. We could publicize a script to fix the problem in any beta5 or RC1 databases that people don't want to re-initdb.
I agree, and this brings up a question that I've pondered before. Why do we ever *require* and initdb when only metadata has changed (i.e. the contents of the system catalogs, not catalog or page structure)?
ISTM that we ought to distinguish between catalog version, meaning something structural has changed, and catalog-data version which is correctible by running a script.
Joe
---------------------------(end of broadcast)--------------------------- TIP 7: don't forget to increase your free space map settings
