| From: | PG Doc comments form <noreply(at)postgresql(dot)org> |
|---|---|
| To: | pgsql-docs(at)lists(dot)postgresql(dot)org |
| Cc: | grega(dot)jesih(at)gmail(dot)com |
| Subject: | text fields and performance for ETL |
| Date: | 2021-11-03 13:29:19 |
| Message-ID: | 163594615980.678.1904941309603792278@wrigleys.postgresql.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-docs |
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.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2021-11-03 14:07:55 | Re: text fields and performance for ETL |
| Previous Message | Bruce Momjian | 2021-11-03 00:37:12 | Re: ldapbindpasswd parameter value encrypted |