From: | Thomas Lockhart <lockhart(at)alumni(dot)caltech(dot)edu> |
---|---|
To: | Larry Rosenman <ler(at)lerctr(dot)org> |
Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Update: mac.c update, patch now on ftp |
Date: | 2000-07-20 06:07:38 |
Message-ID: | 3976972A.8C644672@alumni.caltech.edu |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
> I was thinking of making the following:
> 1) macaddr_manuf function that returns the first 3 octets of a macaddr
> 2) a macaddr_manuf TYPE that can be used for the table
> 3) supply the ouiparse.awk to generate a set of INSERT statements
> to load a table
> 4) allow the above table to be indexed.
Why not use a comparison function which knows how to compare just the
manufacturer's id fields? Or define a function which masks a mac address
to return the id fields and zeros everywhere else (so you can then use
the "normal" comparison functions)?
Defining a new type to allow this masking and comparison seems more than
necessary (which, if this argument holds up, would make it undesirable).
We can still define functional indices so that a table lookup will be
fast in any case.
- Thomas
From | Date | Subject | |
---|---|---|---|
Next Message | Larry Rosenman | 2000-07-20 06:33:33 | Re: Update: mac.c update, patch now on ftp |
Previous Message | Tom Lane | 2000-07-20 05:08:55 | Re: btree split logic is fragile in the presence of lar ge index items |