Re: text fields and performance for ETL - Mailing list pgsql-docs

From David G. Johnston
Subject Re: text fields and performance for ETL
Date
Msg-id CAKFQuwYFfESp=xUpktYBbW8TxO8k=+uWN8F2G5Ehis2cpYuDnw@mail.gmail.com
Whole thread Raw
In response to Re: text fields and performance for ETL  (Grega Jesih <Grega.Jesih@actual-it.si>)
Responses RE: text fields and performance for ETL
List pgsql-docs
On Wed, Nov 3, 2021 at 11:09 AM Grega Jesih <Grega.Jesih@actual-it.si> wrote:

The new architectures include more and more data exchange among databases. 
Now when you deal with bigger data sizes that go from millions to billions, this fixed size vs of text - undefined size becomes very  relevant. 

Can you demonstrate, with actual numbers, using today's implementation, a situation where defining a column as char(3) or varchar(3) instead of text has a significant performance improvement?  Without a concrete example to examine I'm unable to be convinced to move away from the status quo.

You also need to convince me as to why constraints are an insufficient feature.  i.e., why is char(3) better than (check length(val) = 3)?

Even with all that I'd probably still not do anything beyond reviewing a proposed patch (i.e, I wouldn't try to write one myself from scratch...I don't have authority to commit regardless).

David J.

pgsql-docs by date:

Previous
From: Grega Jesih
Date:
Subject: Re: text fields and performance for ETL
Next
From: Tom Lane
Date:
Subject: Re: text fields and performance for ETL