Feedback-ID: i131946ab:Fastmail
Message-ID: <457ba532-ea71-dc13-6d60-2b79bb32eeeb@enterprisedb.com>
Date: Thu, 6 Jul 2023 18:38:27 +0200
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:102.0)
 Gecko/20100101 Thunderbird/102.12.0
Subject: Re: UUID v7
Content-Language: en-US
To: Tom Lane <tgl@sss.pgh.pa.us>, Daniel Gustafsson <daniel@yesql.se>
Cc: Matthias van de Meent <boekewurm+postgres@gmail.com>,
 Nikolay Samokhvalov <samokhvalov@gmail.com>,
 "Kyzer Davis (kydavis)" <kydavis@cisco.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>
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>
 <7AC9F1D2-A02B-4FF6-A331-C686C7EA244B@yesql.se>
 <1204013.1688652164@sss.pgh.pa.us>
From: Peter Eisentraut <peter.eisentraut@enterprisedb.com>
In-Reply-To: <1204013.1688652164@sss.pgh.pa.us>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: <https://www.postgresql.org/message-id/457ba532-ea71-dc13-6d60-2b79bb32eeeb%40enterprisedb.com>
Precedence: bulk

On 06.07.23 16:02, Tom Lane wrote:
> Daniel Gustafsson <daniel@yesql.se> writes:
>> On 6 Jul 2023, at 15:29, Matthias van de Meent <boekewurm+postgres@gmail.com> wrote:
>>> 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.
> 
> We have done a couple of things that way recently.  An important
> reason why we felt we could get away with that is that nowadays
> we have people who actually sit on the SQL committee and have
> reliable information on what's likely to make it into the final text
> of the next version.  I don't think we have equivalent visibility or
> should have equivalent confidence about how UUID v7 standardization
> will play out.

(I have been attending some meetings and I'm on the mailing list.)

Anyway, I think it would be reasonable to review this patch now.  We 
might leave it hanging in "Ready for Committer" for a while when we get 
there.  But surely review can start now.