From: | Vivek Khera <khera(at)kcilink(dot)com> |
---|---|
To: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: Differences between postgres and mysql |
Date: | 2004-02-18 22:09:42 |
Message-ID: | x7isi4kpjt.fsf@yertle.int.kciLink.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
>>>>> "TL" == Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> writes:
TL> Mike Nolan <nolan(at)gw(dot)tssi(dot)com> writes:
>> MySQL's poor implementation of the 'alter table' process.
TL> Interesting you should say that, because for years we were getting beat
TL> up regularly about how poor our ALTER capabilities were compared to
TL> MySQL's. Have we really passed them up in ALTER flexibility? Or is
TL> there some other limitation you are thinking of?
I think we get beat up on the things you can (rather cannot) ALTER. I
think mysql is getting beat up on how they implement the ALTER. From
my readings earlier on this list, it seems that the entire backend
file(s) are copied upon alter, and all indexes rebuilt. That would be
a major PITA for a large database (not that you'd have one all that
large in mysql anyhow ;-))
--
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
Vivek Khera, Ph.D. Khera Communications, Inc.
Internet: khera(at)kciLink(dot)com Rockville, MD +1-301-869-4449 x806
AIM: vivekkhera Y!: vivek_khera http://www.khera.org/~vivek/
From | Date | Subject | |
---|---|---|---|
Next Message | Jeff Davis | 2004-02-18 22:19:14 | Re: Differences between postgres and mysql |
Previous Message | scott.marlowe | 2004-02-18 21:53:59 | Re: [Re] Need help with postgresql/apache/php optimisation |