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 225239FA605 for ; Sun, 2 Jul 2006 12:00:32 -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 74066-09 for ; Sun, 2 Jul 2006 12:00:27 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey- Received: from anchor-post-36.mail.demon.net (anchor-post-36.mail.demon.net [194.217.242.86]) by postgresql.org (Postfix) with ESMTP id DF47B9FA50D for ; Sun, 2 Jul 2006 12:00:26 -0300 (ADT) Received: from mailgate.vale-housing.co.uk ([194.217.48.34] helo=vale-housing.co.uk) by anchor-post-36.mail.demon.net with esmtp (Exim 4.42) id 1Fx3Qv-000H9o-L0 for pgsql-general@postgresql.org; Sun, 02 Jul 2006 15:00:25 +0000 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: quoted-printable X-MimeOLE: Produced By Microsoft Exchange V6.5 Subject: Re: Notes on converting from MySQL 5.0.x to PostgreSQL Date: Sun, 2 Jul 2006 16:00:25 +0100 Message-ID: In-Reply-To: <20060630172939.GB7035@fetter.org> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: [GENERAL] Notes on converting from MySQL 5.0.x to PostgreSQL thread-index: AcacasWZQ0ua4ssQST+HJ/NvyP1sxgBfOoPw From: "Dave Page" To: "David Fetter" Cc: "Scott Marlowe" , "Jason McManus" , "pgsql general" X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200607/37 X-Sequence-Number: 97661 =20 > -----Original Message----- > From: David Fetter [mailto:david@fetter.org]=20 > Sent: 30 June 2006 18:30 > To: Dave Page > Cc: Scott Marlowe; Jason McManus; pgsql general > Subject: Re: [GENERAL] Notes on converting from MySQL 5.0.x=20 > to PostgreSQL >=20 > Last I checked, pgAdmin 1.4 doesn't help setting up clusters, which is > one of the major headaches of a Slony-I setup. I also noticed that > pgAdmin 1.6-to-be has at least some of those hooks. Any ETA on that? It certainly can setup a new cluster - the only feature we don't support is failover because Andreas was never happy with the way it worked and such a critical operation needs to be flawless. That said, don't ask me how to setup a new cluster - I've never actually done it myself (in pgAdmin). Regards, Dave.