Re: Replication and coding good practices

From: Simon Riggs <simon(at)2ndQuadrant(dot)com>
To: David Fetter <david(at)fetter(dot)org>
Cc: Craig Ringer <craig(at)postnewspapers(dot)com(dot)au>, Ivan Sergio Borgonovo <mail(at)webthatworks(dot)it>, "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org>
Subject: Re: Replication and coding good practices
Date: 2009-07-02 16:33:17
Message-ID: 1246552397.27964.496.camel@dn-x300-willij
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general


On Mon, 2009-06-29 at 07:34 -0700, David Fetter wrote:
> On Mon, Jun 29, 2009 at 07:11:43PM +0800, Craig Ringer wrote:
> > On Sun, 2009-06-28 at 09:01 -0700, David Fetter wrote:
> > > > Are there any rules of thumb to consider for making an application
> > > > easier to work with a "general" replication solution?
> > > >
> > > > The applications I mostly deal with are e-commerce sites.
> > >
> > > It really depends on what replication solution you choose, along with
> > > the environment you're deploying into.
> >
> > ... and why you need replication. Reliability/Availability? Data storage
> > redundancy? Performance? And if performance, read-mostly performance or
> > write-heavy performance?
>
> It's this kind of discussion that you might want to hire experts to
> help with :) Commandprompt, Endpoint, OmniTI and the outfit I work
> for, PostgreSQL Experts <http://www.pgexperts.com> would be examples.

Probably should mention 2ndQuadrant also, since we have an Italian
office (for the original poster) and we have been developing replication
for PostgreSQL for some time now.

--
Simon Riggs www.2ndQuadrant.com
PostgreSQL Training, Services and Support

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Simon Riggs 2009-07-02 16:36:05 Re: pgAdmin - no_spool
Previous Message McWilliams, Steven 2009-07-02 16:22:09 compiling postgres for 64 bit windows using mingw64