From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
Cc: | erlkonig(at)talisman(dot)org, pgsql-bugs(at)postgresql(dot)org |
Subject: | Re: BUG #6651: macaddr length constraint violates standard |
Date: | 2012-05-20 16:16:31 |
Message-ID: | 20547.1337530591@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
Peter Eisentraut <peter_e(at)gmx(dot)net> writes:
> On fre, 2012-05-18 at 19:57 +0000, erlkonig(at)talisman(dot)org wrote:
>> Given compatibility concerns, renaming
>> it is probably infeasible. However, being able to parameterize the
>> length, defaulting to 6 bytes, would be adequate.
> That could be a workable solution.
That's far more easily said than done, considering macaddr is a
fixed-length type with essentially no overhead info. I don't see a way
to do this at all without an on-disk compatibility break. Given the
number of requests so far (viz, one) it doesn't seem like something
we should expend much effort on. We might at some point consider
introducing a different type that could handle variable length data
... although it's not clear that text or bytea couldn't meet the
apparently limited need.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2012-05-20 17:27:48 | Re: BUG #6640: pg_dump does not always dump data of tables marked as editable in extension |
Previous Message | Peter Eisentraut | 2012-05-19 23:11:05 | Re: BUG #6642: Spanish collation fault |