Best practice for altering a table
От | Tim Wilson |
---|---|
Тема | Best practice for altering a table |
Дата | |
Msg-id | 200211102234.38921.wilson@visi.com обсуждение исходный текст |
Ответы |
Re: Best practice for altering a table
|
Список | 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@visi.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-----
В списке pgsql-novice по дате отправления: