Re: UUID v7 - Mailing list pgsql-hackers

From Peter Eisentraut
Subject Re: UUID v7
Date
Msg-id 457ba532-ea71-dc13-6d60-2b79bb32eeeb@enterprisedb.com
Whole thread Raw
In response to Re: UUID v7  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: UUID v7
List pgsql-hackers
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.




pgsql-hackers by date:

Previous
From: Andrew Dunstan
Date:
Subject: Re: pg_basebackup check vs Windows file path limits
Next
From: Ranier Vilela
Date:
Subject: Re: Avoid overflow with simplehash