Re: [GENERAL] RE: Why is there so much MySQL bashing???
Tony Grant wrote: That can't be good for PostgreSQL, can it? Neither can not being able to do rpm -Uvh and have it work first time... H... When was the last time you tried? Thanks to the 'Do No Harm' principle, it would be foolhardy to do what has to be done to upgrade between major versions in a fully automatic fashion. So the semiautomatic way it is now done is the current best compromise. Of course, the ideal would be for a new version of PostgreSQL to be able to at least read and convert existing tables on the fly (as in when postmaster is started, or when a backend is first brought up on the table in question, or even a standalone migration utility that doesn't require an old version of the backend to read the old version files), but I wouldn't hold your breath. Yes, the existing scheme is a little baroque -- but it's better than it used to be. -- Lamar Owen WGCR Internet Radio 1 Peter 4:11
Re: [GENERAL] RE: Why is there so much MySQL bashing???
On 2001.01.18 17:31:29 +0100 Lamar Owen wrote: Tony Grant wrote: That can't be good for PostgreSQL, can it? Neither can not being able to do rpm -Uvh and have it work first time... H... When was the last time you tried? Yesterday... The RedHat 6.2 rpms are broken if they find the tiniest trace of a preceding instalation. The machine target for 7.0.3 had a copy of 6.5.x installed when the ReHat server was installed. The database system was initiallised but never used. I removed all traces of the 6.5.x install and did a 7.0.3 install. initdb fails of course because there must be something somewhere that makes it choke. I have installed previous versions from source and spent hours getting permissions right so that initdb would run. Now I just want to set up a new machine and rpm is a convenient way of doing that. When it doesn't work as advertized it is a little "annoying". Any pointers greatly appreciated. Cheers Tony Grant -- It's just some computers connected together...
Re: [GENERAL] RE: Why is there so much MySQL bashing???
Philip Hallstrom wrote: You're right of course, I should have left that out... but my point is still valid. Pointing out the serious limitations in MySQL is not, IMHO, bashing. MySQL currently has serious limitations for many RDBMS uses. Concurrent performance under industry-standard benchmarks in one indicator. I my previous conversations with Monty, anytime I brought up the subject of multiuser benchmarks, he consistently stated that the single-user case was more important, as that's how the current (as of the last time I looked) MySQL 'benchmarks' are structured. Concurrent benchmarking, with a real-world mix of queries (such as AS3AP and TPC-C), is far more useful to those who are using an RDBMS for more than just a web backend. Although, it is a useful average indicator of web backend performance as well. And I have to note that SourceForge switched for performance reasons. Seems there was a great deal of Postgres-bashing from the MySQL side not long ago. -- Lamar Owen WGCR Internet Radio 1 Peter 4:11
