From: Scott Ribe <scott_ribe@killerbytes.com>
To: Russ Brown <pickscrape@gmail.com>
To: Postgres General <pgsql-general@postgresql.org>
Subject: Re: Replication
Date: Tue, 20 Sep 2005 08:21:13 -0600
Message-ID: <BF5576F9.31CB3%scott_ribe@killerbytes.com> (raw)
In-Reply-To: <432B2B82.5030709@gmail.com>
> Indeed. But just to stress the point, I wasn't stating that the included
> replication in MySQL was any good (though it's not terrible as we're
> using it heavily in an extremely high-volume situation with few
> problems), I was just bringing up the idea of getting a decent
> replication solution included in PostgreSQL for relatively little effort.
No, but IIRC, you didn't state that is was a substandard solution, and, also
IIRC, it really sounded as though you believed it was a good one.
>> So, feel free to mention MySQL, but know that mostly when it's mentioned
>> here, it's mentioned as an example of how things shouldn't be done. In
>> terms of coding, marketing, testing, or licensing.
>>
>
> I think in future I'll just stick to not mentioning it. :)
Probably not necessary; just make it clear whether you're saying "MySQL
claims... and it would be good for Postgres to have its own solution..." or
"MySQL has an actual working full-blown good solution for... that Postgres
would do well to emulate".
--
Scott Ribe
scott_ribe@killerbytes.com
http://www.killerbytes.com/
(303) 665-7007 voice
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-general@postgresql.org
Cc: scott_ribe@killerbytes.com, pickscrape@gmail.com
Subject: Re: Replication
In-Reply-To: <BF5576F9.31CB3%scott_ribe@killerbytes.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox