Re: options for logical replication plugins?

From: Chris Withers <chris(at)simplistix(dot)co(dot)uk>
To: Andres Freund <andres(at)anarazel(dot)de>
Cc: "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org>
Subject: Re: options for logical replication plugins?
Date: 2017-03-16 06:50:51
Message-ID: c11871de-9e49-6c50-b103-8f9b35b36b35@simplistix.co.uk
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On 15/03/2017 19:18, Andres Freund wrote:
> Hi,
>
>
> On 2017-03-15 18:29:06 +0000, Chris Withers wrote:
>> Shame the decoding has to be done on the server-side rather than the client
>> side.
>
> Why?

Requiring compiled extensions to be installed on the server is always
going to be a pain, especially in a multi-tenant environment or
something with Amazon or Google's cloud offerings.

> You can't filter on the client side. You don't have any catalog
> information available, so you'd have to transport a lot of metadata and
> / or decode to a verbose default format.

Just to check my understanding: a logical replication stream is
per-database, right?

I'd imagine that for many uses of this functionality, having the "whole
stream" in an efficient, compressed format that could be decoded on the
client side, with any filtering or reshaping done there.

cheers,

Chris

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Alexander Farber 2017-03-16 07:43:40 Re: UPDATE ... ON CONFLICT DO NOTHING
Previous Message Tom Lane 2017-03-15 21:48:10 Re: pg_dump pg_restore hanging in CentOS for large data