Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1mQZwD-0001iy-OT for pgsql-bugs@arkaria.postgresql.org; Wed, 15 Sep 2021 18:47:18 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1mQZwC-0002rl-AB for pgsql-bugs@arkaria.postgresql.org; Wed, 15 Sep 2021 18:47:16 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1mQZwB-0002rd-2A for pgsql-bugs@lists.postgresql.org; Wed, 15 Sep 2021 18:47:16 +0000 Received: from out1-smtp.messagingengine.com ([66.111.4.25]) by makus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1mQZw8-0003eH-9o for pgsql-bugs@lists.postgresql.org; Wed, 15 Sep 2021 18:47:14 +0000 Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.nyi.internal (Postfix) with ESMTP id 314835C00E4; Wed, 15 Sep 2021 14:47:10 -0400 (EDT) Received: from imap21 ([10.202.2.71]) by compute1.internal (MEProxy); Wed, 15 Sep 2021 14:47:10 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=eulerto.com; h= mime-version:message-id:in-reply-to:references:date:from:to :subject:content-type; s=fm2; bh=fqmMJq6HG5PqyM4r4BNyUWLNwAB7W9+ Iri3VqwTMT6U=; b=lj7WPDE/NeT5+2Yv9ztRrApMO/FD7HeBi/qDzgEa48TVxth A56hUP3VSHhmk4PWpiAEA2MqfW2vyQFH1iSBw7PNNHiojFiutzIQfWkWZZoKAOCf yJIYTEDmWntEHuogbBYxyabampplVl8MTNCGy0EURtEA3Ed7h6GKWY40znHS7ATB x6lgJFmGCtD7yCS9+JWlLJ/+fGpVFOQAmHxeYugPzSw8ST5stPlXC3x2oNj2NGNO mG/BP0H2qgdZOG6OnAYKbFTqtkEQrgiEv/HHX/tPZmiHuywuGOneRISjNkTW+zVm n8DmU/V32zK4+RtLeKsj7/n+xMsSbrBF9h+McoQ== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-proxy :x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s=fm3; bh=fqmMJq 6HG5PqyM4r4BNyUWLNwAB7W9+Iri3VqwTMT6U=; b=SS4BMMReMy1DLJVcfYzqUE X3HfEvbd/HULdkjyjbwr2OwlfE6e9aQzsIPSHEAli+z+IYIONHRP7VifVK8N18mg rTWHGu6sdubQKi/vxH3UT4G1Z2fVFPOcx0Rpt35Hx03HHg+ukXDb6Xpm+wVtkKzt QhkL178v/EBp/TNQHV4jHArOPnS8dnG3TlfJldP8Mu93NTIPV2FSywZZ5PxgVigW g9cKmO7aD/G4vcZ0iyIi0TmZfvQ6GSwMk9zPRescKAbKerbcpT2D7OxmZ/PE7JSJ 9tXCtBRJFBtVXQbZLsMKFZSJZWuMBUskUytd3/cDH8uQV0VxY+HNbRc1+RFj0a4Q == X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvtddrudehuddguddvhecutefuodetggdotefrod ftvfcurfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfgh necuuegrihhlohhuthemuceftddtnecunecujfgurhepofgfggfkjghffffhvffutgesrg dtreerreertdenucfhrhhomhepfdfguhhlvghrucfvrghvvghirhgrfdcuoegvuhhlvghr segvuhhlvghrthhordgtohhmqeenucggtffrrghtthgvrhhnpeejtefhuedvgffftdetve dufedtjeeuffekleevkefhveekgeelfefhjeehtdejgeenucffohhmrghinhepvghnthgv rhhprhhishgvuggsrdgtohhmnecuvehluhhsthgvrhfuihiivgeptdenucfrrghrrghmpe hmrghilhhfrhhomhepvghulhgvrhesvghulhgvrhhtohdrtghomh X-ME-Proxy: Received: by mailuser.nyi.internal (Postfix, from userid 501) id B7B3151C0060; Wed, 15 Sep 2021 14:47:09 -0400 (EDT) X-Mailer: MessagingEngine.com Webmail Interface User-Agent: Cyrus-JMAP/3.5.0-alpha0-1291-gc66fc0a3a2-fm-20210913.001-gc66fc0a3 Mime-Version: 1.0 Message-Id: <8eef5dcf-c327-4142-baab-877be77aa994@www.fastmail.com> In-Reply-To: <17193-f78a9d144d26150f@postgresql.org> References: <17193-f78a9d144d26150f@postgresql.org> Date: Wed, 15 Sep 2021 15:46:48 -0300 From: "Euler Taveira" To: sushant.kamboj@getfareye.com, pgsql-bugs@lists.postgresql.org Subject: Re: BUG #17193: Issue with pg_output login Content-Type: multipart/alternative; boundary=c2a2e940f1bc4293aa06c3a80d11c65b List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --c2a2e940f1bc4293aa06c3a80d11c65b Content-Type: text/plain 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 EDB https://www.enterprisedb.com/ --c2a2e940f1bc4293aa06c3a80d11c65b Content-Type: text/html Content-Transfer-Encoding: quoted-printable
On Tue, Sep 14,= 2021, at 10:44 AM, PG Bug reporting form wrote:
We identified that there was an is= sue 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 distorti= on
with the Greek letters.
You = don't provide enough information. What's your database encoding?

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


--
Euler= Taveira
EDB   https://www.enterprisedb.com/
=

--c2a2e940f1bc4293aa06c3a80d11c65b--