Re: [HACKERS] varchar() vs char16 performance - Mailing list pgsql-hackers

From Andrew Martin
Subject Re: [HACKERS] varchar() vs char16 performance
Date
Msg-id 199803121108.LAA08207@bsmir06.biochem.ucl.ac.uk
Whole thread Raw
Responses Re: [HACKERS] varchar() vs char16 performance  (Bruce Momjian <maillist@candle.pha.pa.us>)
List pgsql-hackers
> >
> > > Will there be a warning about using a "depreciated type" in 6.4 or are
> > > we going to have this gunking up the grammer forever? :)
> >
> > Good idea. Then we can pull it out of the grammar sometime later. Now,
> > if these types are in a loadable module, then we can't actually do
> > anything in the parser anyway, since the loadable module would never
> > work. Are these character types worth keeping at all? Less support and
> > no performance benefit leaves me thinking not...
>
> IMHO, not worth keeping if the performance benefit is gone and the only
> real benefit though was the few bytes of header space they saved per field.
>

If char2 et al are going completely from 6.4, I think it would be sensible
for pg_dump to filter these types and change them to char(2) et al when
it writes the CREATE statments.

Best wishes,

Andrew

----------------------------------------------------------------------------
Dr. Andrew C.R. Martin                             University College London
EMAIL: (Work) martin@biochem.ucl.ac.uk    (Home) andrew@stagleys.demon.co.uk
URL:   http://www.biochem.ucl.ac.uk/~martin
Tel:   (Work) +44(0)171 419 3890                    (Home) +44(0)1372 275775

pgsql-hackers by date:

Previous
From: Maarten Boekhold
Date:
Subject: Re: [HACKERS] Re: indexing words slow
Next
From: PostgreSQL
Date:
Subject: Failing to get email from list or to susbscribe