Re: configure --with-uuid=bsd fails on NetBSD
Nazir Bilal Yavuz <byavuz81@gmail.com>
From: Nazir Bilal Yavuz <byavuz81@gmail.com>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Andres Freund <andres@anarazel.de>, pgsql-hackers@lists.postgresql.org
Date: 2022-09-09T14:54:07Z
Lists: pgsql-hackers
Attachments
- v2-0001-error-out-uuid_create-function.patch (text/x-patch) patch v2-0001
Hi, On 8/26/22 19:21, Tom Lane wrote: > Nazir Bilal Yavuz <byavuz81@gmail.com> writes: >> Based on these discussions, I attached a patch. > > I think the right fix is to call uuid_create and then actually check > the version field of the result. This avoids breaking what need not > be broken, and it'd also guard against comparable problems on other > platforms (so don't blame NetBSD specifically in the message, either). I updated my patch. I checked version field in 'uuid_generate_internal' function instead of checking it in 'uuid_generate_v1' and 'uuid_generate_v1mc' functions, but I have some questions: 1 - Should it be checked only for '--with-uuid=bsd' option? 1.1 - If it is needed to be checked only for '--with-uuid=bsd', should just NetBSD be checked? 2 - Should it error out without including current UUID version in the error message? General error message could mask if the 'uuid_create' function starts to produce UUIDs other than version-4. Regards, Nazir Bilal Yavuz
Commits
-
Reject bogus output from uuid_create(3).
- e55ccb3b179c 14.6 landed
- c4b6d218e369 16.0 landed
- a61095aa7946 13.9 landed
- 95028d9de422 10.23 landed
- 4d3f54bd7a0d 11.18 landed
- 23fe89a61223 12.13 landed
- 100a8ca2c285 15.0 landed