Date: Sat, 8 Jan 2022 11:44:54 -0800
From: Andres Freund <andres@anarazel.de>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: byavuz81@gmail.com, pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #17358: While using --with-uuid=bsd option, uuid_ossp test
 fails on NetBSD 9.2
Message-ID: <20220108194454.kl477tb6km6tyj5r@alap3.anarazel.de>
References: <17358-89806e7420797025@postgresql.org>
 <1377833.1641588532@sss.pgh.pa.us>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <1377833.1641588532@sss.pgh.pa.us>
Archived-At: 
 <https://www.postgresql.org/message-id/20220108194454.kl477tb6km6tyj5r%40alap3.anarazel.de>
Precedence: bulk

Hi,

On 2022-01-07 15:48:52 -0500, Tom Lane wrote:
> https://man.netbsd.org/NetBSD-8.2/uuidgen.2
> https://man.netbsd.org/NetBSD-9.0/uuidgen.2
> 
> We hadn't noticed because our one NetBSD 9.x buildfarm animal
> isn't building with --with-uuid :-(.

It's interesting that freebsd seems to continue generating a v1 uuid, given
that the manpage for netbsd says that uuidgen() stems from freebsd.


> Not sure about how to fix this nicely.  We've tried to avoid
> writing our own code for V1 UUIDs, but maybe we should just
> bite the bullet and do that?

It might be the most reasonable approach. We certainly seem to have spent at
least as much effort avoiding our own implementation than implementing it
ourselves.

We could also just have a configure test rejecting netbsd's uuidgen, so that
--with-uuid=bsd wouldn't support it anymore? Presumably forcing e2fs to be
used?


> The hard part seems like it'd be to get a MAC address from someplace.

We could grab it from ossp-uuid or e2fs - both seem to be compatibly licensed?

Greetings,

Andres Freund