| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Greg Stark <gsstark(at)mit(dot)edu>, Peter Eisentraut <peter_e(at)gmx(dot)net>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: autogenerating headers & bki stuff |
| Date: | 2009-07-26 19:25:12 |
| Message-ID: | 603c8f070907261225x174694d7scc96e96af0f931d2@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Sun, Jul 26, 2009 at 1:58 PM, Tom Lane<tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> 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.
Is this mostly a forward-reference problem?
...Robert
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2009-07-26 19:43:28 | Re: CommitFest Status Summary - 2009-07-25 |
| Previous Message | Robert Haas | 2009-07-26 19:23:41 | Re: autogenerating headers & bki stuff |