Re: Sequence vs UUID - Mailing list pgsql-general

From Tom Lane
Subject Re: Sequence vs UUID
Date
Msg-id 497565.1675097323@sss.pgh.pa.us
Whole thread Raw
In response to Re: Sequence vs UUID  (Dominique Devienne <ddevienne@gmail.com>)
Responses Re: Sequence vs UUID
List pgsql-general
Dominique Devienne <ddevienne@gmail.com> writes:
> On Mon, Jan 30, 2023 at 5:11 PM veem v <veema0000@gmail.com> wrote:
>> CREATE TABLE test1_UUID ( id bigint,source_id varchar(36) PRIMARY KEY, Name varchar(20) );

> Maybe if you used a "native" 16-byte uuid, instead of its textual
> serialization with dashes (36 bytes + length overhead), the gap would
> narrow.

Yeah, especially if your database is not using C locale.  The
strcoll or ICU-based comparisons done on string types can be
enormously more expensive than the memcmp() used for binary
types like native uuid.

            regards, tom lane



pgsql-general by date:

Previous
From: Dominique Devienne
Date:
Subject: Re: Sequence vs UUID
Next
From: Alvaro Herrera
Date:
Subject: Re: How could I elog the tupleTableSlot to the fronted terminal?