| From: | "Euler Taveira" <euler(at)eulerto(dot)com> |
|---|---|
| To: | "Sushant Kamboj" <sushant(dot)kamboj(at)getfareye(dot)com>, pgsql-bugs(at)lists(dot)postgresql(dot)org |
| Cc: | "Ashish Kumar" <ashish(dot)kumar2(at)getfareye(dot)com>, "Satyam Chaudhary" <satyam(dot)chaudhary(at)getfareye(dot)com> |
| Subject: | Re: BUG #17193: Issue with pg_output login |
| Date: | 2021-09-21 20:46:50 |
| Message-ID: | 08de48f1-a66e-491c-9841-7ee015a48b6c@www.fastmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
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 binary
output. 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 RDS
You don't provide enough information for an investigation. You can start with a
reproducible test case.
--
Euler Taveira
EDB https://www.enterprisedb.com/
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Gerdan Rezende dos Santos | 2021-09-21 21:09:35 | Re: BUG #17193: Issue with pg_output login |
| Previous Message | Andriy Bartash | 2021-09-21 16:27:06 | Re: BUG #17198: Planning time too high when execute query on standby cluster |