On Sat, Jul 25, 2009 at 9:17 PM, Robert Haas<robertmh...@gmail.com> wrote: > Of course, fixing the Anum and > Natts declarations does not come close to fixing this problem: for > catalogs that are initialized with any data at bootstrap time, the > DATA() lines are a much bigger issue, but fixing that is going to > require a bigger hammer than can be put in place with one patch. I do > think this is a pretty good foundation on which to build, though.
I think addressing that would actually be fairly simple in theory. Move a lot of those DATA lines to SQL initdb scripts. Virtually all of pg_proc, pg_operator, pg_opclass, pg_opfamily, pg_cast, etc can be initialized using SQL. Hardly any of the records in there are needed for bootstrapping. That would reduce the pain of editing this files *enormously*. The worst part of adding new operators is making sure all the opclass entries line up properly. And when there's an OID conflict and they all have to be renumbered and the opclasses fixed up that's when they're a real headache. -- greg http://mit.edu/~gsstark/resume.pdf -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
