RE: text fields and performance for ETL

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(dot)albe(at)cybertec(dot)at>
Sent: Saturday, November 6, 2021 6:28 AM
To: Bruce Momjian <bruce(at)momjian(dot)us>; David G. Johnston <david(dot)g(dot)johnston(at)gmail(dot)com>
Cc: Grega Jesih <Grega(dot)Jesih(at)actual-it(dot)si>; Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>; Pg Docs <pgsql-docs(at)lists(dot)postgresql(dot)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(at)momjian(dot)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 material of 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 destroy all copies of them.