MIME-Version: 1.0
References: <CAB+=1TWZNvMhVthJ2iKs_Q4qBzMw-v_oaSz7HbFE_P_qC5jMFA@mail.gmail.com>
 <3dddea5e-52ab-4075-970d-a87b0c921ae7@aklaver.com>
In-Reply-To: <3dddea5e-52ab-4075-970d-a87b0c921ae7@aklaver.com>
From: veem v <veema0000@gmail.com>
Date: Tue, 17 Sep 2024 09:25:59 +0530
Message-ID: <CAB+=1TWdRd2sBw7-vXCovH_VHLANh+aSaU-WyJ2m8tL4TkF=8g@mail.gmail.com>
Subject: Re: IO related waits
To: Adrian Klaver <adrian.klaver@aklaver.com>, Christophe Pettus <xof@thebuild.com>
Cc: pgsql-general <pgsql-general@lists.postgresql.org>
Content-Type: multipart/alternative; boundary="0000000000008c6633062248ab76"
Archived-At: <https://www.postgresql.org/message-id/CAB%2B%3D1TWdRd2sBw7-vXCovH_VHLANh%2BaSaU-WyJ2m8tL4TkF%3D8g%40mail.gmail.com>
Precedence: bulk

--0000000000008c6633062248ab76
Content-Type: text/plain; charset="UTF-8"

On Tue, 17 Sept 2024 at 03:41, Adrian Klaver <adrian.klaver@aklaver.com>
wrote:

>
> Are you referring to this?:
>
>
> https://nightlies.apache.org/flink/flink-docs-release-1.20/docs/dev/datastream/operators/asyncio/
>
> If not then you will need to be more specific.
>
>
Yes, I was referring to this one. So what can be the caveats in this
approach, considering transactions meant to be ACID compliant as financial
transactions.Additionally I was not aware of the parameter
"synchronous_commit" in DB side which will mimic the synchronous commit.

Would both of these mimic the same asynchronous behaviour and achieves the
same, which means the client data load throughput will increase because the
DB will not wait for those data to be written to the WAL and give a
confirmation back to the client and also the client will not wait for the
DB to give a confirmation back on the data to be persisted in the DB or
not?. Also, as in the backend the flushing of the WAL to the disk has to
happen anyway(just that it will be delayed now), so can this method cause
contention in the database storage side if the speed in which the data gets
ingested from the client is not getting written to the disk , and if it can
someway impact the data consistency for the read queries?

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

<div dir=3D"ltr"><div dir=3D"ltr"><br></div><br><div class=3D"gmail_quote">=
<div dir=3D"ltr" class=3D"gmail_attr">On Tue, 17 Sept 2024 at 03:41, Adrian=
 Klaver &lt;<a href=3D"mailto:adrian.klaver@aklaver.com">adrian.klaver@akla=
ver.com</a>&gt; wrote:<br></div><blockquote class=3D"gmail_quote" style=3D"=
margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-lef=
t:1ex"><br>
Are you referring to this?:<br>
<br>
<a href=3D"https://nightlies.apache.org/flink/flink-docs-release-1.20/docs/=
dev/datastream/operators/asyncio/" rel=3D"noreferrer" target=3D"_blank">htt=
ps://nightlies.apache.org/flink/flink-docs-release-1.20/docs/dev/datastream=
/operators/asyncio/</a><br>
<br>
If not then you will need to be more specific.<br><br></blockquote><div><br=
></div><div>Yes, I was referring to this one. So what can be the caveats in=
 this approach, considering transactions meant to be ACID compliant as fina=
ncial transactions.Additionally I was not aware of the parameter &quot;sync=
hronous_commit&quot; in DB side which will mimic the synchronous commit.</d=
iv><div><br></div><div>Would both of these mimic the same asynchronous beha=
viour and achieves the same, which means the client data load throughput=C2=
=A0will increase because the DB will not wait for those data to be written =
to the WAL and give a confirmation back to the client and also the client w=
ill not wait for the DB to give a confirmation back on the data to be persi=
sted in the DB or not?. Also,=C2=A0as in the backend the flushing of the WA=
L to the disk has to happen anyway(just that it will be delayed now), so ca=
n this method cause contention in the database=C2=A0storage side if the spe=
ed in which=C2=A0the data gets ingested from the client is not getting writ=
ten to the=C2=A0disk , and if it can someway impact the data consistency fo=
r the read queries?</div></div></div>

--0000000000008c6633062248ab76--