Greg Stark <gsstark(at)mit(dot)edu> writes:
> AFAICT the only opclasses that need to be in the bootstrap set are
> int2_ops, int4_ops, name_ops, oid_ops, and oidvector_ops.
Maybe so, but the first two are part of the integer_ops family. If
we have to continue implementing all of that through DATA statements
then we haven't done much towards making things more maintainable
or less fragile. I think we need to try to get *all* of the operator
classes out of the hand-maintained-DATA-entries collection.
The argument about optional stuff doesn't impress me. I would think
that something that's going to be optionally loaded doesn't need to be
considered during bootstrap mode at all. We can just have initdb run
some SQL scripts (or not) during its post-bootstrap phase.
regards, tom lane
In response to
pgsql-hackers by date
|Next:||From: Pavel Stehule||Date: 2009-07-26 18:39:40|
|Subject: query - change in gistentryinit between 8.1 and 8.2|
|Previous:||From: Kevin Grittner||Date: 2009-07-26 17:49:32|
|Subject: Re: When is a record NULL?|