From: | Tilo Sloboda <tilo(dot)sloboda(at)gmail(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | pgsql-bugs(at)postgresql(dot)org |
Subject: | Re: BUG #14362: Postgres macaddr does not support EUI-64 8-byte MAC addresses |
Date: | 2016-10-10 21:41:18 |
Message-ID: | 7d72d1c5-bf3d-17ea-d90a-7e402c708b82@gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
thanks for the quick answer.
I'm not a contributor of the Postgres code base.
The EUI-64 has been around for a while now, and real-world data contains
such MAC addresses.
How useful is the current macaddr data type if it breaks with real world
input data - and in turn end-users apps?
It would be great it either the macaddr type would be extended, or an
additional type could be introduced which can handle both 48 and 64-bit
MACs.
best regards, Tilo
On 10/10/16 10:00 AM, Tom Lane wrote:
> tilo(dot)sloboda(at)gmail(dot)com writes:
>> What is the plan for Postgres to support EUI-64 MACs?
>
> I know of nobody working on that. Feel free to submit a patch.
> (I'm afraid it might be nontrivial to get the current datatype
> to do anything about this, though, since it's hard-wired as 6 bytes
> on-disk.)
>
> regards, tom lane
>
From | Date | Subject | |
---|---|---|---|
Next Message | Noah Misch | 2016-10-11 06:42:18 | Re: language code incompatibility in Windows |
Previous Message | Henry Cate | 2016-10-10 20:59:05 | Re: BUG #14363: CASE against a literal value produces correct against, same expression against a column null doesn't |