Re: [HACKERS] What can we learn from MySQL?
От | Alvar Freude |
---|---|
Тема | Re: [HACKERS] What can we learn from MySQL? |
Дата | |
Msg-id | 309340000.1082754857@gnarzelwicht.delirium-arts.de обсуждение исходный текст |
Ответ на | Re: [HACKERS] What can we learn from MySQL? (pgsql@mohawksoft.com) |
Список | pgsql-advocacy |
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, - -- pgsql@mohawksoft.com wrote: > I would say this is a clear 'NO!' When ever I read about open-source being > used anywhere, I always read MySQL. They are *very* good at this. yes! Some days ago, there was a news in the Heise Newsticker (most important IT news in germany), about MySQL clustering. http://www.heise.de/newsticker/meldung/46511 "4*2 processors with 100000 replicated transactions per second" was the main statement. I'm sure, that this is the typical MySQL blabla: no transactions, but select statements ... <http://www.heise.de/newsticker/foren/go.shtml?read=1&msg_id=5487088&forum_id =55321> I'm not sure, if iot is a good idea to go down with the niveau to such lies. >> o Are we focused enough on ease-of-use issues? > > Again, NO! To often you guys settle for a work-around rather than a > feature. You are satisfied that symlinks will do the job. When someone > says they want a feature, you say, no - use a symlink. [...] yes, you are right! One additional thing: when updating from 7.x to 7.y, a new initdb is needed. This means: If I have some GB Data, the RDBMS is some ours down for upgrading. This is really no good situation. There should be a way for converting the storage on the fly: Updating and let postgres do the rest automaically. I guess this is not really easy; but it is important! Ciao Alvar - -- ** Alvar C.H. Freude -- http://alvar.a-blast.org/ -- http://odem.org/ ** Berufsverbot? http://odem.org/aktuelles/staatsanwalt.de.html ** ODEM.org-Tour: http://tour.odem.org/ ** 5 Jahre Blaster: http://www.a-blast.de/ | http://www.a-blast.de/statistik/ -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.3 (FreeBSD) iD8DBQFAiYcpOndlH63J86wRAoj7AKCt+SXIV/1UYa7hZlEpA1SrwpctnQCgpypM 2L5aRteQ7btVuBowcclBc28= =POHj -----END PGP SIGNATURE-----
В списке pgsql-advocacy по дате отправления: