From: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
---|---|
To: | Alex Pilosov <alex(at)pilosoft(dot)com> |
Cc: | Larry Rosenman <ler(at)lerctr(dot)org>, Thomas Lockhart <lockhart(at)alumni(dot)caltech(dot)edu>, pgsql-hackers(at)hub(dot)org |
Subject: | Re: mac.c |
Date: | 2000-07-27 13:00:25 |
Message-ID: | 200007271300.JAA04830@candle.pha.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
> It'd be nice (tm). I am using mac address types now, and certainly going
> to be upset if they just disappear in next postgres version :P)
No, I don't recommend removing the macaddr type. It is fine in the main
tree. It is just the function that maps ethernet address to
manufacturer that I am questioning.
>
> However, this is definitely a contrib feature, not a core postgres item.
>
> Probably the macaddr type should be also moved to that contrib directory.
>
> I suggest that the contrib would include a query that creates mac_manuf
> table and a 'macaddr_manuf(macaddr) returns varchar' function which would
> do a 'select name from mac_manuf m where m.mac=mac_trunc(macaddr)' and a
> 'mac_trunc(macaddr) returns macaddr' which would set the 3 lowest-order
> nibbles to 0.
>
> (I don't think macmanufacturer deserves a separate type).
--
Bruce Momjian | http://candle.pha.pa.us
pgman(at)candle(dot)pha(dot)pa(dot)us | (610) 853-3000
+ If your life is a hard drive, | 830 Blythe Avenue
+ Christ can be your backup. | Drexel Hill, Pennsylvania 19026
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 2000-07-27 13:06:32 | Re: About these IPC parameters |
Previous Message | Olivier PRENANT | 2000-07-27 11:00:04 | Arrays how to... |