From: | Tim Wilson <wilson(at)visi(dot)com> |
---|---|
To: | pgsql-novice(at)postgresql(dot)org |
Subject: | Best practice for altering a table |
Date: | 2002-11-11 04:34:09 |
Message-ID: | 200211102234.38921.wilson@visi.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-novice |
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi everyone,
I've done a fair bit of googling on this, but I haven't come to a conclusion
about the recommended procedure for altering some datatypes in a particular
table. Not surprisingly, I've discovered that some of my VARCHARs are not
long enough and I need to change them.
What is "best practice" for this sort of thing? BTW, I'm running PG 7.1.3 on
Debian 3.0.
On a related note, I assume that besides being PostgreSQL-specific, the
tradeoff for the TEXT datatype's flexibility is speed. If that's correct,
how much is the speed penalty on a database that's pretty lightly used?
(Few INSERTs, fair number of SELECTs.)
- -Tim
- --
Tim Wilson
Twin Cities, Minnesota, USA
Science teacher, Linux fan, Zope developer, Grad. student, Daddy
mailto:wilson(at)visi(dot)com | http://qwerk.org/ | public key: 0x8C0F8813
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.7 (GNU/Linux)
iD8DBQE9zzNVB56RQ4wPiBMRAldVAKCTSJ33jGjJLzowDWlqVAaSVl85/gCgtC53
dWQYuq/nUsU0AgbQjuNLfoI=
=1IcI
-----END PGP SIGNATURE-----
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2002-11-11 05:16:01 | Re: Best practice for altering a table |
Previous Message | Tom Lane | 2002-11-10 17:49:16 | Re: Authentification |