Date: Mon, 20 May 2024 05:33:37 -0700 (PDT)
From: Rich Shepard <rshepard@appl-ecosys.com>
To: pgsql-general <pgsql-general@lists.postgresql.org>
Subject: Re: Updating 457 rows in a table
In-Reply-To: <7F273F19-168F-4C66-85C5-B4BA8395E7A6@gmail.com>
Message-ID: <eb6da387-986c-bed6-3e17-21bed5da872@appl-ecosys.com>
References: <164b3681-7a42-1e5-6a7b-80196ed33ded@appl-ecosys.com> <1E14886A-BBCB-40E4-8231-1159D12BD261@thebuild.com> <98639d1a-dddf-38e3-49b3-63632136a0f@appl-ecosys.com> <372F0968-BD78-45EB-AE70-015DBF923EBC@thebuild.com> <7e82178c-1249-b592-bfea-5152563ceb4c@appl-ecosys.com>
 <7F273F19-168F-4C66-85C5-B4BA8395E7A6@gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8BIT
Archived-At: <https://www.postgresql.org/message-id/eb6da387-986c-bed6-3e17-21bed5da872%40appl-ecosys.com>
Precedence: bulk

On Mon, 20 May 2024, Alban Hertroys wrote:

> That aside, while you’re not absolutely 100% definitely sure that an
> UPDATE or DELETE statement is going to do exactly what you intended, and
> for good measure if you are, wrapping such statements in a transaction
> allows you to ROLLBACK to get back to the state that you started from.

Alban,

That's excellent advice and I'll do so in all future data manipulation
scripts. In the current situation psql did return that 457 rows had been
updated.

Much appreciated,

Rich