Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1ncsvJ-0001Ky-8H for pgsql-general@arkaria.postgresql.org; Fri, 08 Apr 2022 18:01:29 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1ncsvI-0006ya-3b for pgsql-general@arkaria.postgresql.org; Fri, 08 Apr 2022 18:01:28 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1ncsvH-0006yR-Pi for pgsql-general@lists.postgresql.org; Fri, 08 Apr 2022 18:01:27 +0000 Received: from mail-oi1-x234.google.com ([2607:f8b0:4864:20::234]) by makus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.92) (envelope-from ) id 1ncsvF-0004au-Jy for pgsql-general@lists.postgresql.org; Fri, 08 Apr 2022 18:01:26 +0000 Received: by mail-oi1-x234.google.com with SMTP id z8so9615313oix.3 for ; Fri, 08 Apr 2022 11:01:25 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=message-id:date:mime-version:user-agent:subject:content-language:to :references:from:in-reply-to; bh=4vkm047qmt966+Wvio4fFx6lDsIvmml+bsEmLxbdf20=; b=FO9sqohjKhd9vaFnqYhhfptsxlwocBW7TbS1Cq1A7hnXfXKqf6si4+nYwOqLqnI9/6 Cg7jO6HrUsgndSGO3OAy/Dd2br2K/NZ3udD4kIjIBvUiGbGASwAwt6OImU4vgRyXGCqY TJX26aB5TAqTtzp70C4VbAHUrodJfnK1XkWVgGfgbQddTJvMhi3F6PLumtGL+0V3ISY7 6V6GPU7ByvJg1R/GhkoeCSSr2XPl1pvyDZbrS0LeMqBTnM8xlS26bYSwPfqb0uL13Fyh AnUyXjzk0TsTiDgRikFhfuPMXwbJAEn8Tp+uJ5J0b2MaJjo6MDpYZRLdqofH8OeLqyCY BPxQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:message-id:date:mime-version:user-agent:subject :content-language:to:references:from:in-reply-to; bh=4vkm047qmt966+Wvio4fFx6lDsIvmml+bsEmLxbdf20=; b=KA6AEevkT2gn82NojK7ypIzV+ut+yiln07/DdHqf10vuprOzE1KmQyHyWYN+cTHu0K /AkNUWNsLeFaDfSGOjdLnO0mSiDnch2P+yTTtMdfyza9vKmfoItnSGN7vOx5q2OPLAeu mNsxEkORuNWnsvH5YDXkF0Kfs3DiHIVBTBvOLuCHvpXxcrvs9GeRtmScskBcoT/HVYX5 DIV+WYdQTWfgZ134FxQnryWpnHjw0FtDRX7WOVkoR4t/ctigLuRPsIsVm6uERtSwslCI ktATDPZbQq/ooDBM1Zmzb5dIvF8Br6C5sUewHE7TyILuP6ydila1chO/fA9a7jHyrycK 7UmQ== X-Gm-Message-State: AOAM5309Avrvx7mwvodEP2w3vlMTEep49T0u0M8NiAiK1ypq7fvyOgtP 05aDkZ3JXnZCjQNN6xsOteZPus1QOUk= X-Google-Smtp-Source: ABdhPJyUjBOQcETYD+mkXTaqHAk3as/LAT0pbsC7bHspd9Rh7sSdEGBb+/LOouhciOVByYFQrFn+JA== X-Received: by 2002:a05:6808:2088:b0:2f7:d63a:c28b with SMTP id s8-20020a056808208800b002f7d63ac28bmr470746oiw.141.1649440884419; Fri, 08 Apr 2022 11:01:24 -0700 (PDT) Received: from [192.168.88.10] (ip68-11-68-85.no.no.cox.net. [68.11.68.85]) by smtp.googlemail.com with ESMTPSA id j72-20020a9d17ce000000b005e6b89f9f54sm1631057otj.32.2022.04.08.11.01.23 for (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Fri, 08 Apr 2022 11:01:23 -0700 (PDT) Content-Type: multipart/alternative; boundary="------------tEhEQI5S8bqGxNb357gq0dVO" Message-ID: Date: Fri, 8 Apr 2022 13:01:23 -0500 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:91.0) Gecko/20100101 Thunderbird/91.5.0 Subject: Re: Long running processes and commit writing to disk Content-Language: en-US To: pgsql-general@lists.postgresql.org References: From: Ron In-Reply-To: List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk This is a multi-part message in MIME format. --------------tEhEQI5S8bqGxNb357gq0dVO Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit 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. --------------tEhEQI5S8bqGxNb357gq0dVO Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit 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.
--------------tEhEQI5S8bqGxNb357gq0dVO--