Skip site navigation (1) Skip section navigation (2)

Peripheral Links

Header And Logo

PostgreSQL
| The world's most advanced open source database.

Site Navigation

Search archives
  Advanced Search

Re: draft RFC: concept for partial, wal-based replication


  • From: Stefan Kaltenbrunner <stefan(at)kaltenbrunner(dot)cc>
  • To: Andres Freund <andres(at)anarazel(dot)de>
  • Cc: pgsql-hackers(at)postgresql(dot)org, Itagaki Takahiro <itagaki(dot)takahiro(at)oss(dot)ntt(dot)co(dot)jp>, Boszormenyi Zoltan <zb(at)cybertec(dot)at>, hs(at)cybertec(dot)at
  • Subject: Re: draft RFC: concept for partial, wal-based replication
  • Date: Mon, 30 Nov 2009 10:32:50 +0100
  • Message-id: <4B139142.1030109@kaltenbrunner.cc> <text/plain>

Andres Freund wrote:
On Monday 30 November 2009 03:57:11 Itagaki Takahiro wrote:
Boszormenyi Zoltan <zb(at)cybertec(dot)at> wrote:
we tried to discuss on a lower level what should be needed
for a partial replication based on streaming replication.
We need to discuss a "partial recovery" before the partial replication.
If you do the filtering on the sending side you dont actually need partial recover in the sense that you filter in the rmgr or similar.

Or do I miss something?

the question is if filtering on the sending side is actually the "right thing" to do. It increases the overhead and the complexity on the master, especially if you think about different (partial) replication agreements for different slaves and it might also be hard to integrate with the planned sync/async modes. On the other hand if you filter on the master you might be able to avoid a lot of network traffic du to filtered wal records. I think for a first step it might make more sense to look into doing the filtering on the receiving side and look into actual integration with SR at a later stage.


Stefan



Home | Main Index | Thread Index

Privacy Policy | About PostgreSQL
Copyright © 1996 – 2012 PostgreSQL Global Development Group