MIME-Version: 1.0
References: 
 <CA+i5JwbqHrQNPjWgUzcQWTs3XueGuxp82RZ4FAZ-P8dhRk22CA@mail.gmail.com>
 <CA+i5JwYicGdvXLSNx_VdREEuCCWch2gWevK6avSQfPM2EgDwEQ@mail.gmail.com>
In-Reply-To: 
 <CA+i5JwYicGdvXLSNx_VdREEuCCWch2gWevK6avSQfPM2EgDwEQ@mail.gmail.com>
From: Shaozhong SHI <shishaozhong@gmail.com>
Date: Fri, 8 Apr 2022 17:39:50 +0100
Message-ID: 
 <CA+i5JwYJ173ehMH7bfRvDyhAd0JwhFG5dV4U=4jgfe6uuoeizw@mail.gmail.com>
Subject: Long running processes and commit writing to disk
To: pgsql-general <pgsql-general@lists.postgresql.org>
Content-Type: multipart/alternative; boundary="000000000000ecaa0305dc273eb2"
Archived-At: 
 <https://www.postgresql.org/message-id/CA%2Bi5JwYJ173ehMH7bfRvDyhAd0JwhFG5dV4U%3D4jgfe6uuoeizw%40mail.gmail.com>
Precedence: bulk

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

When long running processes got disrupted, one may not see any expected
result.

How to make sure that the result of each operation is saved to disk in a
loop?

Regards,

David

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

<div dir=3D"ltr"><div class=3D"gmail_quote"><div dir=3D"ltr"><div class=3D"=
gmail_quote"><br><div dir=3D"ltr">When long running processes got disrupted=
, one may not see any expected result.<div><br></div><div>How to make sure =
that the result of each operation is saved to disk in a loop?</div><div><br=
></div><div>Regards,</div><div><br></div><div>David</div></div>
</div></div>
</div></div>

--000000000000ecaa0305dc273eb2--