From: | Merlin Moncure <mmoncure(at)gmail(dot)com> |
---|---|
To: | Andres Freund <andres(at)2ndquadrant(dot)com> |
Cc: | pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: [PATCH 16/16] current version of the design document |
Date: | 2012-06-13 14:21:12 |
Message-ID: | CAHyXU0y8tqBbX7JLgiWJsiN+tOL54e=tXbi4tGig+cjJ_GERfw@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Wed, Jun 13, 2012 at 6:28 AM, Andres Freund <andres(at)2ndquadrant(dot)com> wrote:
> +synchronized catalog at the decoding site. That adds some complexity to use
> +cases like replicating into a different database or cross-version
> +replication. For those it is relatively straight-forward to develop a proxy pg
> +instance that only contains the catalog and does the transformation to textual
> +changes.
wow. Anyways, could you elaborate on a little on how this proxy
instance concept would work? Let's take the case where I have N
small-ish schema identical database shards that I want to aggregate
into a single warehouse -- something that HS/SR currently can't do.
There's a lot of ways to do that obviously but assuming the warehouse
would have to have a unique schema, could it be done in your
architecture?
merlin
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2012-06-13 14:35:31 | Re: [COMMITTERS] pgsql: Mark JSON error detail messages for translation. |
Previous Message | Amit Kapila | 2012-06-13 14:06:41 | Re: WIP patch for Todo Item : Provide fallback_application_name in contrib/pgbench, oid2name, and dblink |