From: | Radoslaw Stachowiak <radek(at)alter(dot)pl> |
---|---|
To: | "PostgreSQL::General List" <pgsql-general(at)postgreSQL(dot)org> |
Subject: | Re: [Solved] SQL Server to PostgreSQL |
Date: | 2000-09-01 18:12:08 |
Message-ID: | 20000901201208.O5017@blue.alter.pl |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general pgsql-hackers |
*** Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> [Tuesday, 22.August.2000, 23:11 -0400]:
> There's no essential performance difference between char(n), varchar(n),
> and text in Postgres, given the same-sized data value. char(n)
> truncates or blank-pads to exactly n characters; varchar(n) truncates
> if more than n characters; text never truncates nor pads. Beyond that
> they are completely identical in storage requirements.
[.rs.]
Does varchar(188) takes 188 bytes (+ bytes for length storage) every
time, no matter if it contains 'my text' or 'my long 188 char text.....'
?
--
radoslaw.stachowiak.........................................http://alter.pl/
From | Date | Subject | |
---|---|---|---|
Next Message | Radoslaw Stachowiak | 2000-09-01 18:51:52 | Re: Large object insert performance. |
Previous Message | Dave Smith | 2000-09-01 18:02:17 | Re: Increasing system speed by using -F option |
From | Date | Subject | |
---|---|---|---|
Next Message | Nataraj | 2000-09-01 19:05:25 | Postgres startup problem |
Previous Message | Thomas Lockhart | 2000-09-01 16:21:07 | Re: [7.0.2] Negative OIDs? |