RE: text fields and performance for ETL

Поиск
Список
Период
Сортировка
От Grega Jesih
Тема RE: text fields and performance for ETL
Дата
Msg-id 2def7f5785d042b1b4a11d6b712b39a5@actual-it.si
обсуждение исходный текст
Ответ на Re: text fields and performance for ETL  (Laurenz Albe <laurenz.albe@cybertec.at>)
Список pgsql-docs
Dear Moderators,

with this approach, why don't you eliminate char and varchar then ?
Thanks for thinking over.

BR
Grega

-----Original Message-----
From: Laurenz Albe <laurenz.albe@cybertec.at>
Sent: Saturday, November 6, 2021 6:28 AM
To: Bruce Momjian <bruce@momjian.us>; David G. Johnston <david.g.johnston@gmail.com>
Cc: Grega Jesih <Grega.Jesih@actual-it.si>; Tom Lane <tgl@sss.pgh.pa.us>; Pg Docs <pgsql-docs@lists.postgresql.org>
Subject: Re: text fields and performance for ETL

On Fri, 2021-11-05 at 11:27 -0400, Bruce Momjian wrote:
> On Fri, Nov  5, 2021 at 07:32:12AM -0700, David G. Johnston wrote:
> > On Friday, November 5, 2021, Bruce Momjian <bruce@momjian.us> wrote:
> >
> >
> >     >
> >     > Perhaps, right before the tip you quoted, something like that:
> >     >
> >     >   If your use case requires a length limit on character data,
> > or
> >     compliance
> >     >   with the SQL standard is important, use "character varying".
> >     >   Otherwise, you are usually better off with "text".
> >
> >     I can support that if others think it is valuable.
> >
> >
> >
> > The motivating complaint is that we should be encouraging people to
> > use varchar
> > (4000) instead of text so external tools can optimize.  If we are
> > not going to do that I really don’t see the pointing in changing
> > away from out current position of “only use text”.  True length
> > limit requirements for data are rare, and better done in constraints
> > along with all other the other constraint that may exist for the
> > data.  I believe comments with respect to the SQL standard are already present and adequate.
>
> Agreed.

+1, so let's leave it as it is.

Yours,
Laurenz Albe


NOTICE - NOT TO BE REMOVED.
This e-mail and any attachments are confidential and may contain legally privileged information and/or copyright
materialof Actual I.T. or third parties. If you are not an authorised recipient of this e-mail, please contact Actual
I.T.immediately by return email or by telephone or facsimile on the above numbers.
 
You should not read, print, re-transmit, store or act in reliance on this email or any attachments and you should
destroyall copies of them.
 

В списке pgsql-docs по дате отправления:

Предыдущее
От: Peter Eisentraut
Дата:
Сообщение: Re: Add link to unicode collation docs
Следующее
От: PG Doc comments form
Дата:
Сообщение: Ltree pattern matching