Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1trft1-007C2l-8Q for pgsql-general@arkaria.postgresql.org; Mon, 10 Mar 2025 16:21:51 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.94.2) (envelope-from ) id 1trfsz-00EpOa-VU for pgsql-general@arkaria.postgresql.org; Mon, 10 Mar 2025 16:21:49 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1trfsz-00EpOE-KH for pgsql-general@lists.postgresql.org; Mon, 10 Mar 2025 16:21:49 +0000 Received: from mail-yw1-x112d.google.com ([2607:f8b0:4864:20::112d]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.96) (envelope-from ) id 1trfsw-0024HE-16 for pgsql-general@lists.postgresql.org; Mon, 10 Mar 2025 16:21:49 +0000 Received: by mail-yw1-x112d.google.com with SMTP id 00721157ae682-6f768e9be1aso57291597b3.0 for ; Mon, 10 Mar 2025 09:21:47 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1741623706; x=1742228506; darn=lists.postgresql.org; h=to:subject:message-id:date:from:mime-version:from:to:cc:subject :date:message-id:reply-to; bh=X0R9J8Dp5OH+zHByYqem03NNXTqvgJOoYpPqRjRi/k0=; b=aGgjwnUPS4UmawS19THCn7ZBJuc0zSUGQXtUSeHB34v0Ablz2M3nYjmUaH1abqdMDd 5ycVG5Fmdd7+t3kiw0+dfEwaGoppUXWdkh4lCBZfknDroGsWCaNUD1vkdqnt+a1i7kTc elLCSzok+xWUkAzzHIM6OJip78l9zB3eVCvJ/o4J6piYRZv5CTISP/ZMWQkVAidbpwmd HZjJQU+NnMkKfA+bw4szndejFdY1IgFT9CVqp4Bn6sBUcXOznNvj0iRkjHLsgZV6+/2D hgRa5OJNMymnRPlIKAggVH+GgDBnSq9rxb3sYd44BunIxJLwe/qPPOf5AQM+EhKVyQA1 xw8A== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1741623706; x=1742228506; h=to:subject:message-id:date:from:mime-version:x-gm-message-state :from:to:cc:subject:date:message-id:reply-to; bh=X0R9J8Dp5OH+zHByYqem03NNXTqvgJOoYpPqRjRi/k0=; b=vslv1VCadLII3S7pDnNIiCDHi/FF4G8SYWu/3dPT7KNr1bo7ZYsvpzV7VFegrMFsT3 kX6r2bhcfnzs+ZEEirZdYkYibSnSUHhCwWGG8o5CxMN3zEdaSBJ+tllAmdPF7vWPx6rG tsuwiJyJzCOBPnXomU1IggXva/E87uh2CKDcG/SNfpQz4/qL52Hq0XLzBcgh8T3n68dr xnukQISUhDZ16GGj8jpJwnisntVDN6SENfxZLWq3tXCvuT0m8gTgAUeszG90QN7XUUlb HdH9wR2f+fF6DZ0COUTZEgCWw8rafkA30myNUIvw1As5qGaDmf7AbgjnPU6rlFFFRVyH ZciQ== X-Gm-Message-State: AOJu0YxadMxuH0DIlLbTAmWJ3HfulZa3V9up3asUtNruCDa7n4UZLNFU SYYMrM4+gHsFfXXWinTIoj/b20QS+iciNkg+W/UGXb0lPlA6O1uErzK0Zi01v3Ik++vmdLh+Jkn q+Xbon0ReVTRnBaHAS0prrL6lsYYTAQ== X-Gm-Gg: ASbGncuSXtRweasY/gkGIkaFwsCPcsLVBdsIwBvNHymnnSE8BqZysM0aaoBleZCe9HN WmB9koDwXabNsJ6fpi7Fc73dwW/7tkruGDEACzHO9UMSXLR+72bLfZ8nvSN25rQp60w/u+PBBPM TguYIDW4cCNaqt8ERvNvt/oCV7xVkO+9B1xnw/DA== X-Google-Smtp-Source: AGHT+IHe3fCb4mnMYVXhIg/OW2ZQstLjAmY1zXb5Wf9pGI+9do+el0CY28A6EbJcnXAWRDM+RF5EEadZ+pfuos1lO2U= X-Received: by 2002:a05:690c:610f:b0:6fb:a251:2450 with SMTP id 00721157ae682-6ff0a290bd2mr1572427b3.1.1741623705974; Mon, 10 Mar 2025 09:21:45 -0700 (PDT) MIME-Version: 1.0 From: Igor Korot Date: Mon, 10 Mar 2025 16:42:24 -0500 X-Gm-Features: AQ5f1Jr3FodW9wfkuT_0aWO66rB9_V-QEAbkiBOslvinyZ3Fwasus7FPu68IqkU Message-ID: Subject: Big script execution To: "pgsql-generallists.postgresql.org" Content-Type: text/plain; charset="UTF-8" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk Hi, ALL, I am trying to execute a huge script (~40K lines) that will populate my database. The script starts with "BEGIN TRANSACTION" and will end with "COMMIT". however I'd like to rollback if there is an error encounter. When I execute it from the Terminal I do use -v ON_ERROR_STOP=1 but I'd like to rolback the transaction so it starts a fresh every time. Is there some kind of ON ERROR ROLLBACK command I can put inside the script? Thank you.