Content-Type: text/plain;
	charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3696.120.41.1.3\))
Subject: Re: UUID v7
From: Daniel Gustafsson <daniel@yesql.se>
In-Reply-To: <CAEze2WhHf8WURmcqu4ZxS7HFzVxPxK4jXUijnPu-easySjgZWg@mail.gmail.com>
Date: Thu, 6 Jul 2023 15:43:06 +0200
Cc: Nikolay Samokhvalov <samokhvalov@gmail.com>,
 "Kyzer Davis (kydavis)" <kydavis@cisco.com>,
 Peter Eisentraut <peter.eisentraut@enterprisedb.com>,
 Andres Freund <andres@anarazel.de>,
 Andrey Borodin <amborodin86@gmail.com>,
 PostgreSQL Hackers <pgsql-hackers@postgresql.org>,
 "brad@peabody.io" <brad@peabody.io>,
 "wolakk@gmail.com" <wolakk@gmail.com>
Content-Transfer-Encoding: quoted-printable
Message-Id: <7AC9F1D2-A02B-4FF6-A331-C686C7EA244B@yesql.se>
References: <CAAhFRxitJv=yoGnXUgeLB_O+M7J2BJAmb5jqAT9gZ3bij3uLDA@mail.gmail.com>
 <20230211011453.uq2yopunpbovcbnn@awork3.anarazel.de>
 <5ceb7394-7488-d438-0951-fcc940feb539@enterprisedb.com>
 <PH0PR11MB5029DF5E0A0EAF8E3CC2C652BBA29@PH0PR11MB5029.namprd11.prod.outlook.com>
 <CANNMO+L9pmgrEZPLhpRrjRcTnzMKgzURSeWFofuKfbHJT9euiA@mail.gmail.com>
 <5176A0E4-CA75-47D0-A1F3-FBC9B6116595@yesql.se>
 <CAEze2WhHf8WURmcqu4ZxS7HFzVxPxK4jXUijnPu-easySjgZWg@mail.gmail.com>
To: Matthias van de Meent <boekewurm+postgres@gmail.com>
Archived-At: <https://www.postgresql.org/message-id/7AC9F1D2-A02B-4FF6-A331-C686C7EA244B%40yesql.se>
Precedence: bulk

> On 6 Jul 2023, at 15:29, Matthias van de Meent =
<boekewurm+postgres@gmail.com> wrote:
>=20
> On Thu, 6 Jul 2023 at 14:24, Daniel Gustafsson <daniel@yesql.se> =
wrote:
>>=20
>>> On 22 Jun 2023, at 20:30, Nikolay Samokhvalov =
<samokhvalov@gmail.com> wrote:
>>=20
>>> Some small updates as I see them:
>>> - there is revision 7 now in =
https://github.com/ietf-wg-uuidrev/rfc4122bis
>>> - noticing that there is no commitfest record, I created one:
>>=20
>> I will actually go ahead and close this entry in the current CF, not =
because we
>> don't want the feature but because it's unlikely that it will go in =
now given
>> that standardization is still underway.  Comitting anything right now =
seems
>> premature, we might as well wait for standardization given that we =
have lots of
>> time before the v17 freeze.
>=20
> I'd like to note that this draft has recently had its last call
> period, and has been proposed for publishing early last month.

Sure, but this document is in AD Evaluation and there are many stages =
left in
the IESG process, it may still take a fair bit of time before this is =
done.

> Sure, it's earlier than the actual release of
> the standard, but that wasn't a blocker for SQL features that were
> considered finalized either.

I can't speak for any SQL standard features we've committed before being
standardized, it's for sure not the norm for the project.  I'm only =
commenting
on this particular Internet standard which we have plenty of time to =
commit
before v17 without rushing to beat a standards committee.

Also, if you look you can see that I moved it to the next CF in a vague =
hope
that standardization will be swift (which is admittedly never is).

--
Daniel Gustafsson