From: | Euler Taveira <euler(at)timbira(dot)com(dot)br> |
---|---|
To: | Kyotaro HORIGUCHI <horiguchi(dot)kyotaro(at)lab(dot)ntt(dot)co(dot)jp>, noriyoshi(dot)shinoda(at)hpe(dot)com |
Cc: | pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: Logical Replication and Character encoding |
Date: | 2017-02-02 03:45:46 |
Message-ID: | ab71bbfd-7af2-91d3-a914-4ef99abc3bb7@timbira.com.br |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 01-02-2017 00:05, Kyotaro HORIGUCHI wrote:
> - Subscriber connects with client_encoding specification and the
> output plugin pgoutput decide whether it accepts the encoding
> or not. If the subscriber doesn't, pgoutput send data without
> conversion.
>
I don't think storage without conversion is an acceptable approach. We
should provide options to users such as ignore tuple or NULL for
column(s) with conversion problem. I wouldn't consider storage data
without conversion because it silently show incorrect data and we
historically aren't flexible with conversion routines.
--
Euler Taveira Timbira - http://www.timbira.com.br/
PostgreSQL: Consultoria, Desenvolvimento, Suporte 24x7 e Treinamento
From | Date | Subject | |
---|---|---|---|
Next Message | David Rowley | 2017-02-02 03:50:04 | Re: pg_authid.rolpassword format (was Re: Password identifiers, protocol aging and SCRAM protocol) |
Previous Message | Tom Lane | 2017-02-02 03:32:52 | Re: TRAP: FailedAssertion("!(hassrf)", File: "nodeProjectSet.c", Line: 180) |