Hi,
3.2.23 was a LONG time ago. One thing I like about mysql is that they are
constantly making major improvements. I have asked this before, where is
Replication with PostgreSQL? If there was a system that could handle more
than one master without hacking, I would seriously look into switching to
PostgreSQL again. Currently mysql can't handle more than one master cleanly.
Lack of built in Replication is the main thing that continues to keep us
from using PostgreSQL. All of the little, "baby can't learn how to program
or write SQL functions" don't do crap for me, but Replication is a large
part of our network structure, we can't do without it and we certainly don't
want to use a third party product. Patching together tools like what happens
with a qmail install is not a system I want to be responsible for. And yet I
like qmail a great deal, and I like what I have seen of PostgreSQL.
Thanks,
Eric
At 10:19 PM 6/22/03 -0400, Tom Lane wrote:
>Bruce Momjian <pgman@candle.pha.pa.us> writes:
>> Interesting thread (php-dev subj: removing bundled libmysql):
>> http://marc.theaimsgroup.com/?l=php-dev&m=105621066832429&w=2
>
>Hoo boy. Did you catch the part about
>
>>> and the MySQL 3.2.23
>>> library can't connect to MySQL 4.1 servers, rendering it broken.
>
>Backwards compatibility must not be a consideration over there...
>
>> We need to use this opportunity to encourage PHP folks to switch to
>> PostgreSQL.
>
>Indeed. What can we do exactly?
>
> regards, tom lane
>
>---------------------------(end of broadcast)---------------------------
>TIP 2: you can get off all lists at once with the unregister command
> (send "unregister YourEmailAddressHere" to majordomo@postgresql.org)
>
(250) 655 - 9513 (PST Time Zone)
"Inquiry is fatal to certainty." -- Will Durant