MIME-Version: 1.0
From: Scott Laird <slaird2016@fau.edu>
Date: Fri, 19 May 2023 14:22:49 -0400
Message-ID: 
 <CAG5DDWBOk_-+iOHq5Fbwk+Kn3qkgFwmoDE7BY4JPn=G0tCvVcw@mail.gmail.com>
Subject: Connection Types with Logical Replication functions
To: psycopg@postgresql.org
Content-Type: multipart/alternative; boundary="000000000000cd738605fc1002e0"
Archived-At: 
 <https://www.postgresql.org/message-id/CAG5DDWBOk_-%2BiOHq5Fbwk%2BKn3qkgFwmoDE7BY4JPn%3DG0tCvVcw%40mail.gmail.com>
Precedence: bulk

--000000000000cd738605fc1002e0
Content-Type: text/plain; charset="UTF-8"

Hi, I was curious about the usage of synchronous connections with
read_message. The documentation says that consume_message should be used
with synchronous connections and that read_message is for async
connections. I noticed during development that you could call read_message
on a synchronous connection and was curious about the repercussions - if
any - would be. Would it make sense to implement a check on calling
read_message to make sure that an async connection is set? Thanks!

--000000000000cd738605fc1002e0
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Hi, I was curious about the usage of synchronous=C2=A0conn=
ections with read_message. The documentation says that consume_message shou=
ld be used with synchronous connections and that read_message is for async =
connections. I noticed during development that you could call read_message =
on a synchronous connection and was curious about the repercussions - if an=
y - would be. Would it make sense to implement a check on calling read_mess=
age to make sure that an async connection is set? Thanks!</div>

--000000000000cd738605fc1002e0--