Re: postgre vs MySQL - Mailing list pgsql-general

From jose javier parra sanchez
Subject Re: postgre vs MySQL
Date
Msg-id 99f1636c0803120947w520e95f2j448cab19b403f260@mail.gmail.com
Whole thread Raw
In response to Re: postgre vs MySQL  (Ivan Sergio Borgonovo <mail@webthatworks.it>)
Responses Re: postgre vs MySQL  (Ivan Sergio Borgonovo <mail@webthatworks.it>)
List pgsql-general
Take a look at pgpool . http://pgpool.projects.postgresql.org/
2008/3/12, Ivan Sergio Borgonovo <mail@webthatworks.it>:
> On Wed, 12 Mar 2008 09:13:14 -0700
>  paul rivers <rivers.paul@gmail.com> wrote:
>
>  > For a database of InnoDB tables, people tend to replicate the
>  > database, and then backup the slave (unless the db is trivially
>
>
> That recalled me the *unsupported* feeling I have that it is easier
>  to setup a HA replication solution on MySQL.
>
>  Pardon my ignorance of serious DBA jargon...
>
>  I'm thinking to something suited for load balancing the read as
>  highest priority in terms of performance *and* duplicate the write
>  across different boxes without the application layer has to know
>  about it as second priority in terms of performance...
>
>  I just would like to be contradicted and pointed to some viable
>  (easy?) setup for pgsql, so that I and other people will get rid of
>  this preconception if any.
>
>
>  --
>  Ivan Sergio Borgonovo
>  http://www.webthatworks.it
>
>
>
>  --
>  Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
>  To make changes to your subscription:
>  http://www.postgresql.org/mailpref/pgsql-general
>

pgsql-general by date:

Previous
From: dmp
Date:
Subject: Re: pain of postgres upgrade with extensions
Next
From: "Gauthier, Dave"
Date:
Subject: Can't rename an existnig DB because it doesn't exist???