Re: BUG #17193: Issue with pg_output login - Mailing list pgsql-bugs

From Sushant Kamboj
Subject Re: BUG #17193: Issue with pg_output login
Date
Msg-id CAG5CZqLQiKghV+x-T28eru-1oAnzQpEk4y=GxLQ9t5wHvwG6BQ@mail.gmail.com
Whole thread Raw
In response to Re: BUG #17193: Issue with pg_output login  ("Euler Taveira" <euler@eulerto.com>)
Responses Re: BUG #17193: Issue with pg_output login  ("Euler Taveira" <euler@eulerto.com>)
List pgsql-bugs
Hi Euler,

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 .

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 RDS

On Thu, Sep 16, 2021 at 12:17 AM Euler Taveira <euler@eulerto.com> wrote:
On Tue, Sep 14, 2021, at 10:44 AM, PG Bug reporting form wrote:
We identified that there was an issue with the encoding with UTF8 characters
with pg_output plugin. The data was visible correctly in the database but
while pushing the data through the CDC pipeline there was some distortion
with the Greek letters.
You don't provide enough information. What's your database encoding?

IIRC Debezium only supports database whose encoding is UTF-8. Since pgoutput
doesn't do encoding conversion and it uses binary output, it seems the issue is
in the Debezium side.


--
Euler Taveira



--

Thanks and Regards
Sushant Kamboj
Database Administrator
+91-9999518201

pgsql-bugs by date:

Previous
From: Sushant Kamboj
Date:
Subject: Re: BUG #17193: Issue with pg_output login
Next
From: Duncan Sands
Date:
Subject: Query planning on partitioned table causes postgres 13.4 to consume all memory