Re: text fields and performance for ETL
От | Bruce Momjian |
---|---|
Тема | Re: text fields and performance for ETL |
Дата | |
Msg-id | 20211103140755.GD5273@momjian.us обсуждение исходный текст |
Ответ на | text fields and performance for ETL (PG Doc comments form <noreply@postgresql.org>) |
Список | 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@momjian.us> https://momjian.us EDB https://enterprisedb.com If only the physical world exists, free will is an illusion.
В списке pgsql-docs по дате отправления: