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

From Hal Snyder
Subject Re: [HACKERS] varchar() vs char16 performance
Date
Msg-id 199803111715.LAA09970@crocodile.vail
Whole thread Raw
In response to varchar() vs char16 performance  ("Thomas G. Lockhart" <lockhart@alumni.caltech.edu>)
Responses Re: [HACKERS] varchar() vs char16 performance  (Brett McCormick <brett@work.chicken.org>)
List pgsql-hackers
> Date: Wed, 11 Mar 1998 14:39:23 +0000
> From: "Thomas G. Lockhart" <lockhart@alumni.caltech.edu>
...
> The char2,4,8,16 types seem to have no value-added over the
> better-supported char(), varchar(), text types; I am considering
> removing them from the backend, and instead have the parser
> transparently translate the types into varchar() (or char() - I'm not
> certain which is a better match for the types) for v6.4. Applications
> would not have to be changed.
>
> Comments?

I'm not up on the details of PostgreSQL's differing character types,
but wonder - would the proposed change break any apps where trailing
(or leading?)  whitespace is significant?  Not that I'm running any
...


pgsql-hackers by date:

Previous
From: darrenk@insightdist.com (Darren King)
Date:
Subject: Re: [HACKERS] varchar() vs char16 performance
Next
From: "Kent S. Gordon"
Date:
Subject: Re: [HACKERS] postgres/alpha problems