From: | Bruce Momjian <bruce(at)momjian(dot)us> |
---|---|
To: | grega(dot)jesih(at)gmail(dot)com, pgsql-docs(at)lists(dot)postgresql(dot)org |
Subject: | Re: text fields and performance for ETL |
Date: | 2021-11-03 14:07:55 |
Message-ID: | 20211103140755.GD5273@momjian.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-docs |
On Wed, Nov 3, 2021 at 01:29:19PM +0000, PG Doc comments form wrote:
> The following documentation comment has been logged on the website:
>
> Page: https://www.postgresql.org/docs/9.6/datatype-character.html
> Description:
>
> Text field is a field that is intended for very big texts.
> Performance within Postgres database is commented to be the same as for
> normal varchar.
>
> But performance in ETL processes related to such data type is decreased
> dramatically, because any process that takes this kind of data needs to
> calculate its size on a row level and cannot take bigger chunks of data
> based on max size.
>
> So the conclusion would be to use an appropriate character length that
> reflects max string size.
I have no idea what you are saying above. There is no additional
overhead for TEXT vs VARCHAR() in Postgres so it seems like an overhead
in applications.
--
Bruce Momjian <bruce(at)momjian(dot)us> https://momjian.us
EDB https://enterprisedb.com
If only the physical world exists, free will is an illusion.
From | Date | Subject | |
---|---|---|---|
Next Message | David G. Johnston | 2021-11-03 14:38:19 | Re: text fields and performance for ETL |
Previous Message | PG Doc comments form | 2021-11-03 13:29:19 | text fields and performance for ETL |