X-Original-To: pgsql-general-postgresql.org@postgresql.org Received: from localhost (mx1.hub.org [200.46.208.251]) by postgresql.org (Postfix) with ESMTP id 57E929FB258 for ; Tue, 11 Jul 2006 12:57:35 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.208.251]) (amavisd-new, port 10024) with ESMTP id 77792-03 for ; Tue, 11 Jul 2006 12:57:24 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey- Received: from exchange.g2switchworks.com (mail.g2switchworks.com [63.87.162.25]) by postgresql.org (Postfix) with ESMTP id B1AAD9FB1CE for ; Tue, 11 Jul 2006 12:57:21 -0300 (ADT) Received: from 10.10.1.37 ([10.10.1.37]) by exchange.g2switchworks.com ([10.10.1.2]) with Microsoft Exchange Server HTTP-DAV ; Tue, 11 Jul 2006 15:57:19 +0000 Received: from state.g2switchworks.com by mail.g2switchworks.com; 11 Jul 2006 10:57:19 -0500 Subject: Re: Notes on converting from MySQL 5.0.x to PostgreSQL From: Scott Marlowe To: Jan Wieck Cc: Alex Turner , Jason McManus , pgsql general In-Reply-To: <44B3C79B.5080006@Yahoo.com> References: <1151680333.13129.55.camel@state.g2switchworks.com> <44B2E595.9060209@Yahoo.com> <33c6269f0607101900s3ba3ad21ncb1dd1df4cf52315@mail.gmail.com> <44B3C79B.5080006@Yahoo.com> Content-Type: text/plain Content-Transfer-Encoding: 7bit Message-Id: <1152633439.6540.65.camel@state.g2switchworks.com> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.6 (1.4.6-2) Date: Tue, 11 Jul 2006 10:57:19 -0500 X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200607/389 X-Sequence-Number: 98013 On Tue, 2006-07-11 at 10:45, Jan Wieck wrote: > On 7/10/2006 10:00 PM, Alex Turner wrote: > > > http://dev.mysql.com/doc/refman/5.1/en/replication-row-based.html > > > > 5.1 > > Ah, thanks. So I guess 5.1.5 and 5.1.8 must be considered major feature > minor/bugfix releases. I still don't understand how people can use > software in production that has literally zero bugfix upgrade path > without the risk of incompatibility due to new features. I consider > every IT manager, who makes that choice, simply overpaid. Dear god! That page made my eyes bleed. Individual users can choose the method of replication for their sessions? There's a mixed method that switches back and forth? "In addition to switching the logging format manually, a slave server may switch the format automatically." I'm pretty sure this kind of thing would never get into PostgreSQL. It's like reading a map of a minefield drawn in crayon.