Re: Long running processes and commit writing to disk

From: Ron <ronljohnsonjr(at)gmail(dot)com>
To: pgsql-general(at)lists(dot)postgresql(dot)org
Subject: Re: Long running processes and commit writing to disk
Date: 2022-04-08 18:01:23
Message-ID: da996cfc-042a-2a52-06aa-3224e857cb64@gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general pgsql-sql

On 4/8/22 11:39, Shaozhong SHI wrote:
>
> 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?

That would of course depend on how often you begin and commit transactions.

--
Angular momentum makes the world go 'round.

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Adrian Klaver 2022-04-08 18:07:06 Re: FOR integer loop bug?
Previous Message Pavel Stehule 2022-04-08 17:58:46 Re: FOR integer loop bug?

Browse pgsql-sql by date

  From Date Subject
Next Message Shaozhong SHI 2022-04-10 13:50:32 How best to do parallel query given tens of thousands of iteration of a loop of recursive queries?
Previous Message Rob Sargent 2022-04-08 17:05:08 Re: Long running processes and commit writing to disk