From: PG Doc comments form <noreply@postgresql.org>
To: pgsql-docs@lists.postgresql.org
Cc: grega.jesih@gmail.com
Subject: text fields and performance for ETL
Date: Wed, 03 Nov 2021 13:29:19 +0000
Message-ID: <163594615980.678.1904941309603792278@wrigleys.postgresql.org> (raw)
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.
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-docs@postgresql.org
Cc: noreply@postgresql.org, pgsql-docs@lists.postgresql.org, grega.jesih@gmail.com
Subject: Re: text fields and performance for ETL
In-Reply-To: <163594615980.678.1904941309603792278@wrigleys.postgresql.org>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox