Skip site navigation (1) Skip section navigation (2)

Re: [INTERFACES] (libpq question) Holy cow, what's all this fluff?!

From: Matthew Hagerty <matthew(at)venux(dot)net>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: pgsql-interfaces(at)postgresql(dot)org
Subject: Re: [INTERFACES] (libpq question) Holy cow, what's all this fluff?!
Date: 1999-02-14 19:09:18
Message-ID: 4.1.19990214140611.00950100@mail.venux.net (view raw or flat)
Thread:
Lists: pgsql-interfaces
At 01:45 PM 2/14/99 -0500, Tom Lane wrote:
>Matthew Hagerty <matthew(at)venux(dot)net> writes:
>> At 04:30 AM 2/14/99 +0000, Thomas G. Lockhart wrote:
>>>> You want a varchar (or is it bpchar?), not a char. char(x) will always 
>>>> return x characters, with space padding if necessary.
>
>> Yeah, but the docs say you get a performance hit for using varchar, text,
>> and the like.  Which is worse, the database performance hit or the extra
>> call to trim for every char field?
>
>Whatever docs you are looking at are obsolete.  char(n), varchar(n), and
>text have essentially interchangeable performance and representation.
>They all have a length word and some characters.
>
>(I've griped about that myself --- particularly that plain "char" is
>effectively an 8-byte field, not a 1-byte field like you'd expect.
>Nobody else seems worried about it though.)
>
>I'd recommend using "text", personally, unless you have a specific
>reason for imposing an upper length limit on the string.
>
>			regards, tom lane

The docs that mention the performance hit were really the FAQ, item 3.10.
Check it out.  Also, item 3.8 mentions psql's \do command, however when I
type \do nothing happens and I have to ctrl-c to get the prompt back.  Any
suggestions?  All I need to do is a case-insensitive query.

Thanks,
Matthew




In response to

pgsql-interfaces by date

Next:From: Wolfgang HottgenrothDate: 1999-02-14 19:44:55
Subject: Pg from CGI in Apache
Previous:From: Ken J. WrightDate: 1999-02-14 19:04:56
Subject: ODBC authentication failure

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group