Re: WIP partial replication patch - Mailing list pgsql-hackers

From Josh Berkus
Subject Re: WIP partial replication patch
Date
Msg-id 4C65AB17.9080505@agliodbs.com
Whole thread Raw
In response to Re: WIP partial replication patch  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: WIP partial replication patch  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
>  Another rather basic problem is that you've
> got to pass system catalog updates downstream (in case they affect
> the tables being replicated) but if you want partial replication then
> many of those updates will be incorrect for the slave machine.

Couldn't this be taken care of by replicating the objects but not any
data for them?  That is, the tables and indexes would exist, but be empty?

> More generally, though, we are going to have our hands full for the
> foreseeable future trying to get the existing style of replication
> bug-free and performant.  I don't think we want to undertake any large
> expansion of the replication feature set, at least not for some time
> to come.  So you can count on me to vote against committing anything
> like this into core.

I imagine it'll take more than a year to get this to work, if we ever
do.  Probably good to put it on a git branch and that way those who want
to can continue long-term work on it.

--                                  -- Josh Berkus                                    PostgreSQL Experts Inc.
                        http://www.pgexperts.com
 


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: review: psql: edit function, show function commands patch
Next
From: Andrew Dunstan
Date:
Subject: Re: patch: General purpose utility functions used by the JSON data type