Re: BUG #17193: Issue with pg_output login
| От | Gerdan Rezende dos Santos |
|---|---|
| Тема | Re: BUG #17193: Issue with pg_output login |
| Дата | |
| Msg-id | CAKOcMA4eQQCT+GL5WCoRr069G0oSpVtiWauvwsj-4O2dELw5KQ@mail.gmail.com обсуждение исходный текст |
| Ответ на | Re: BUG #17193: Issue with pg_output login ("Euler Taveira" <euler@eulerto.com>) |
| Список | pgsql-bugs |
On Tue, Sep 21, 2021 at 5:47 PM Euler Taveira <euler@eulerto.com> wrote:
On Thu, Sep 16, 2021, at 9:36 AM, Sushant Kamboj wrote:As we have verified in our environment ,your above statement looks like a contradiction since this is working fine when we are using wal2json plugin instead of pgoutput .The main difference is: wal2json uses text output and pgoutput uses binaryoutput. I'm not sure if it matters for Debezium.Since pgoutput is a native plugin, kindly let us know any settings or parameter change that we can do to fix this on postgresql or debezium side.FYI:We are using postgresql 12.5 RDSYou don't provide enough information for an investigation. You can start with areproducible test case.--Euler Taveira
At Debezium documentation at [Debezium connector for PostgreSQL :: Debezium Documentation], we can see:
Debezium currently supports databases with UTF-8 character encoding only. With a single byte character encoding, it is not possible to correctly process strings that contain extended ASCII code characters.
Debezium currently supports databases with UTF-8 character encoding only. With a single byte character encoding, it is not possible to correctly process strings that contain extended ASCII code characters.
I believe this is not PostgreSQL BUG, but a Debezium Limitation.
В списке pgsql-bugs по дате отправления: