Re: [GENERAL] options for logical replication plugins? - Mailing list pgsql-general

From Chris Withers
Subject Re: [GENERAL] options for logical replication plugins?
Date
Msg-id c11871de-9e49-6c50-b103-8f9b35b36b35@simplistix.co.uk
Whole thread Raw
In response to Re: [GENERAL] options for logical replication plugins?  (Andres Freund <andres@anarazel.de>)
List 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


pgsql-general by date:

Previous
From: Tom Lane
Date:
Subject: Re: [GENERAL] pg_dump pg_restore hanging in CentOS for large data
Next
From: Alexander Farber
Date:
Subject: Re: [GENERAL] UPDATE ... ON CONFLICT DO NOTHING