Re: BUG #19583: macaddr input accepts octet fields longer than 8 hex digits

From: Daniel Gustafsson <daniel(at)yesql(dot)se>
To: Zexin Li <lizi(dot)openmind(at)gmail(dot)com>
Cc: malis(at)pgrust(dot)com, pgsql-bugs(at)lists(dot)postgresql(dot)org
Subject: Re: BUG #19583: macaddr input accepts octet fields longer than 8 hex digits
Date: 2026-08-01 19:16:01
Message-ID: A063FFD7-094E-42DF-B220-842D133BAA6F@yesql.se
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

> On 1 Aug 2026, at 03:40, Zexin Li <lizi(dot)openmind(at)gmail(dot)com> wrote:

Thanks for the patch!

> * Two undocumented forms that were previously accepted with the correct
> value become errors: fields zero-padded past two digits
> ('001:00:2b:01:02:03') and 0x-prefixed fields ('0xff:0:0:0:0:0').
> Neither can be produced by macaddr_out, so dumps and restores are
> unaffected; the tightening would only bite text held outside the
> database (COPY input, application SQL) that relies on those forms.

This doesn't seem like something we can backpatch though. Our tools might not
produce them, but they may exist in queries and 3rd party tooling which should
not break in a minor rev. I'm not convinced that either of these should be
promoted to errors even in a major rev.

--
Daniel Gustafsson

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message PG Bug reporting form 2026-08-02 01:10:18 BUG #19595: Three memory-safety defects in src/backend/tsearch/spell.c (dictionary loader), PG 18.3
Previous Message Andrey Rachitskiy 2026-08-01 16:50:20 Re: BUG #19594: to_char/jsonpath format cache serves a format tree parsed in the wrong strict-mode