pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Aldor <an@mediaroot.de>
To: pgsql-admin@postgresql.org
Subject: Re: Replication
Date: Fri, 23 Sep 2005 10:12:33 +0100
Message-ID: <4333C701.2080107@mediaroot.de> (raw)
In-Reply-To: <200509201250.27031.cservin@cromagnon.com>
References: <432A83E5.1000507@gmail.com>
	<1127161471.30120.111.camel@state.g2switchworks.com>
	<20050920172802.GK7630@pervasive.com>
	<200509201250.27031.cservin@cromagnon.com>

>Are there any non-statement level solution?  Something that appends to

the WAL

>> on the slave server?


For this kind of solution I'm also looking for a while - but in the
meantime you can also take a look at "slony" - it can do really many
things. Don't give up at the beginning, after you've understood how it
works you will like it  ;-)

Craig Servin wrote:
> Are there any non-statement level solution?  Something that appends to the WAL 
> on the slave server?
> 
> 
> 
> On Tuesday 20 September 2005 12:28 pm, Jim C. Nasby wrote:
> 
>>There's also pgcluster, but keep in mind that these are all
>>statement-level replication solutions which have some rather big
>>gotchas.
>>
>>On Mon, Sep 19, 2005 at 03:24:31PM -0500, Scott Marlowe wrote:
>>
>>>On Mon, 2005-09-19 at 02:02, the vespadict wrote:
>>>
>>>>Hi ,
>>>>
>>>>I want high Availability but I don't need load balance. I need sync
>>>>replication if is posible using two way.
>>>
>>>If you need sync, then pgpool may be a good choice, or client side
>>>replication like C-JDBC or something like that.
>>>
>>>pgpool doesn't HAVE to do load balancing, it can do simple two way sync
>>>replication if that's what you need.
>>>
>>>---------------------------(end of broadcast)---------------------------
>>>TIP 1: if posting/reading through Usenet, please send an appropriate
>>>       subscribe-nomail command to majordomo@postgresql.org so that your
>>>       message can get through to the mailing list cleanly
> 
> 
> ---------------------------(end of broadcast)---------------------------
> TIP 4: Have you searched our list archives?
> 
>                http://archives.postgresql.org
> 



view thread (63+ messages)  latest in thread

Message-ID: <4333C701.2080107@mediaroot.de>
Permalink:  ../4333C701.2080107@mediaroot.de/
Also on:    postgresql.org/message-id/4333C701.2080107@mediaroot.de

 · 

reply

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 from your mail client; the link fills in
  the headers below: reply via email
  Some clients, webmail especially, drop In-Reply-To and References from
  a link, and the reply then starts a new thread: use the mbox below.

  To: pgsql-admin@postgresql.org
  Cc: an@mediaroot.de
  Subject: Re: Replication
  In-Reply-To: <4333C701.2080107@mediaroot.de>
  References: <432A83E5.1000507@gmail.com> <1127161471.30120.111.camel@state.g2switchworks.com> <20050920172802.GK7630@pervasive.com> <200509201250.27031.cservin@cromagnon.com> <4333C701.2080107@mediaroot.de>

* 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