public inbox for [email protected]
help / color / mirror / Atom feedRe: Unexpected data when subscribing to logical replication slot
2+ messages / 2 participants
[nested] [flat]
* Re: Unexpected data when subscribing to logical replication slot
@ 2024-05-08 15:17 Adrian Klaver <[email protected]>
2024-05-08 15:24 ` Re: Unexpected data when subscribing to logical replication slot Daniel McKenzie <[email protected]>
0 siblings, 1 reply; 2+ messages in thread
From: Adrian Klaver @ 2024-05-08 15:17 UTC (permalink / raw)
To: Daniel McKenzie <[email protected]>; pgsql-general
>
> We have found two things that appear to resolve the problem -
>
> * Using a more powerful EC2 instance. We can reproduce the issue with
> a r7a.medium instance but not with a r7a.large EC2 instance.
> * Changing the Postgres synchronous_commit parameter from "on" to
> "off". We cannot reproduce the issue with synchronous_commit set to
> "off".
What is running on the EC2 instance?:
1) The Postgres server.
2) The replication receiver.
3) Both.
>
> We need help to understand this unexpected behaviour.
>
> We are using Postgres 14.10.
>
> Thanks,
> Daniel McKenzie
--
Adrian Klaver
[email protected]
^ permalink raw reply [nested|flat] 2+ messages in thread
* Re: Unexpected data when subscribing to logical replication slot
2024-05-08 15:17 Re: Unexpected data when subscribing to logical replication slot Adrian Klaver <[email protected]>
@ 2024-05-08 15:24 ` Daniel McKenzie <[email protected]>
0 siblings, 0 replies; 2+ messages in thread
From: Daniel McKenzie @ 2024-05-08 15:24 UTC (permalink / raw)
To: Adrian Klaver <[email protected]>; +Cc: pgsql-general
It's running both (in docker containers) and also quite a few more docker
containers running various .NET applications.
Daniel McKenzie
Software Developer
Office: +1 403.910.5927 x 251
Mobile: +44 7712 159045
Website: www.curvedental.com
*Curve Dental Confidentiality Notice*
This message is intended exclusively for the individual or entity to which
it is addressed. This communication may contain information that is
proprietary, privileged, confidential, or otherwise legally exempt from
disclosure. If you are not the named addressee, you are not authorized to
read, print, retain, copy, or disseminate this message or any part of it.
If you have received this message in error, please notify the sender
immediately by replying to this e-mail and delete all copies of this
message.
On Wed, May 8, 2024 at 4:17 PM Adrian Klaver <[email protected]>
wrote:
>
> >
> > We have found two things that appear to resolve the problem -
> >
> > * Using a more powerful EC2 instance. We can reproduce the issue with
> > a r7a.medium instance but not with a r7a.large EC2 instance.
> > * Changing the Postgres synchronous_commit parameter from "on" to
> > "off". We cannot reproduce the issue with synchronous_commit set to
> > "off".
>
> What is running on the EC2 instance?:
>
> 1) The Postgres server.
>
> 2) The replication receiver.
>
> 3) Both.
>
>
> >
> > We need help to understand this unexpected behaviour.
> >
> > We are using Postgres 14.10.
> >
> > Thanks,
> > Daniel McKenzie
>
> --
> Adrian Klaver
> [email protected]
>
>
^ permalink raw reply [nested|flat] 2+ messages in thread
end of thread, other threads:[~2024-05-08 15:24 UTC | newest]
Thread overview: 2+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2024-05-08 15:17 Re: Unexpected data when subscribing to logical replication slot Adrian Klaver <[email protected]>
2024-05-08 15:24 ` Daniel McKenzie <[email protected]>
This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox