Re: autogenerating headers & bki stuff - Mailing list pgsql-hackers

From Robert Haas
Subject Re: autogenerating headers & bki stuff
Date
Msg-id 603c8f070907261225x174694d7scc96e96af0f931d2@mail.gmail.com
Whole thread Raw
In response to Re: autogenerating headers & bki stuff  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: autogenerating headers & bki stuff  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
On Sun, Jul 26, 2009 at 1:58 PM, Tom Lane<tgl@sss.pgh.pa.us> wrote:
> Greg Stark <gsstark@mit.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.

Is this mostly a forward-reference problem?

...Robert


pgsql-hackers by date:

Previous
From: Robert Haas
Date:
Subject: Re: autogenerating headers & bki stuff
Next
From: Robert Haas
Date:
Subject: Re: CommitFest Status Summary - 2009-07-25