Re: [HACKERS] Logical Replication and Character encoding - Mailing list pgsql-hackers

From Peter Eisentraut
Subject Re: [HACKERS] Logical Replication and Character encoding
Date
Msg-id 60c3a111-e602-e10a-e69f-c9fa8ea3c5ad@2ndquadrant.com
Whole thread Raw
In response to Re: [HACKERS] Logical Replication and Character encoding  (Peter Eisentraut <peter.eisentraut@2ndquadrant.com>)
Responses Re: [HACKERS] Logical Replication and Character encoding  ("Shinoda, Noriyoshi" <noriyoshi.shinoda@hpe.com>)
List pgsql-hackers
On 2/17/17 10:14, Peter Eisentraut wrote:
> Well, it is sort of a libpq connection, and a proper libpq client should
> set the client encoding, and a proper libpq server should do encoding
> conversion accordingly.  If we just play along with this, it all works
> correctly.
> 
> Other output plugins are free to ignore the encoding settings (just like
> libpq can send binary data in some cases).
> 
> The attached patch puts it all together.

committed

-- 
Peter Eisentraut              http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services



pgsql-hackers by date:

Previous
From: Masahiko Sawada
Date:
Subject: [HACKERS] Report the number of skipped frozen pages by manual VACUUM
Next
From: Simon Riggs
Date:
Subject: Re: [HACKERS] dropping partitioned tables without CASCADE