| From: | Julien Rouhaud <julien(dot)rouhaud(at)dalibo(dot)com> |
|---|---|
| To: | Craig Ringer <craig(at)2ndquadrant(dot)com>, Haribabu Kommi <kommi(dot)haribabu(at)gmail(dot)com> |
| Cc: | "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: macaddr 64 bit (EUI-64) datatype support |
| Date: | 2016-10-12 08:42:20 |
| Message-ID: | c56b48bb-3f3d-0195-6373-c710248501aa@dalibo.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 12/10/2016 09:32, Craig Ringer wrote:
> On 12 October 2016 at 14:30, Haribabu Kommi <kommi(dot)haribabu(at)gmail(dot)com> wrote:
>
>> As we are moving to PostgreSQL 10, so are there any plans of backward
>> compatiblity
>> breakage, so the existing macaddr datatype itself can be changed to support
>> both
>> 48 and 64 bit MAC addresses. If not, I will try update the POC patch with
>> more details
>> similar like macaddr datatype.
>
> There's been some minor BC breaking, but breaking on-disk format for
> pg_upgrade is a much bigger deal. I'm really not a fan of that idea.
>
> Just use macaddr64 if you want wide MACs.
>
>
+1
and you can instead make macaddr64 support both format, and provide a
macaddr::macaddr64 cast
--
Julien Rouhaud
http://dalibo.com - http://dalibo.org
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Albe Laurenz | 2016-10-12 09:09:05 | Add PGDLLEXPORT to PG_FUNCTION_INFO_V1 |
| Previous Message | Michael Paquier | 2016-10-12 08:11:06 | Re: Password identifiers, protocol aging and SCRAM protocol |