| From: | Ian Turner <vectro(at)pipeline(dot)com> |
|---|---|
| To: | Jan Wieck <janwieck(at)Yahoo(dot)com> |
| Cc: | Martin Christensen <knightsofspamalot-factotum(at)mail1(dot)stofanet(dot)dk>, pgsql-general(at)postgresql(dot)org |
| Subject: | Re: [Solved] SQL Server to PostgreSQL |
| Date: | 2000-09-03 01:18:22 |
| Message-ID: | Pine.LNX.4.21.0009021817420.4481-100000@crafter.house |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general pgsql-hackers |
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
> From 7.1 on the system will try to compress all types
> internally stored as variable length (char(), varchar(), text
> and some more). So the real amount of bytes for a char(188)
> will be "at maximum 192 - probably less".
Don't variable-length records incur a performance overhead? In this case,
ought I be able to specify the length for a record if I know ahead of time
it will be the same in every case? :o
Ian Turner
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.1 (GNU/Linux)
Comment: For info see http://www.gnupg.org
iD8DBQE5sabgfn9ub9ZE1xoRAhayAKCwMjh/5tYlg8zZiAimJlgFSfCLsQCghBce
Gxx6X8sSwIACIHvdbxBsgGQ=
=bogc
-----END PGP SIGNATURE-----
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Mark Kirkwood | 2000-09-03 04:05:08 | RE:7.1 Release date ( Actually 7.1 Upgrade ) |
| Previous Message | Jan Wieck | 2000-09-02 23:53:48 | Re: PL/Perl compilation error |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2000-09-03 05:07:28 | Re: [Solved] SQL Server to PostgreSQL |
| Previous Message | Jan Wieck | 2000-09-02 23:53:48 | Re: PL/Perl compilation error |