May 14, 2026 - The savepoint remains valid and can be rolled back to again later, if needed. ROLLBACK TO SAVEPOINT implicitly destroys all savepoints that were established after the named savepoint.

May 14, 2026 - BEGIN; INSERT INTO table1 VALUES (1); SAVEPOINT my_savepoint; INSERT INTO table1 VALUES (2); SAVEPOINT my_savepoint; INSERT INTO table1 VALUES (3); -- rollback to the second savepoint ROLLBACK TO SAVEPOINT my_savepoint; SELECT * FROM table1; -- shows rows 1 and 2 -- release the second savepoint RELEASE SAVEPOINT my_savepoint; -- rollback to the first savepoint ROLLBACK TO SAVEPOINT my_savepoint; SELECT * FROM table1; -- shows only row 1 COMMIT;

May 14, 2026 - The savepoint remains valid and can be rolled back to again later, if needed. ROLLBACK TO SAVEPOINT implicitly destroys all savepoints that were established after the named savepoint.

November 13, 2025 - The savepoint remains valid and can be rolled back to again later, if needed. ROLLBACK TO SAVEPOINT implicitly destroys all savepoints that were established after the named savepoint.

May 14, 2026 - The savepoint remains valid and can be rolled back to again later, if needed. ROLLBACK TO SAVEPOINT implicitly destroys all savepoints that were established after the named savepoint.

November 22, 2023 - To roll back to the savepoint, use the below command `ROLLBACK TO <savepoint name>;` At the end of the Business Logic, use a COMMIT or ROLLBACK, as per the need. However, the transition to PostgreSQL may raise questions about the relevance of ...

July 1, 2021 - BEGIN; UPDATE users SET gems = gems — 100 WHERE id=1;SAVEPOINT point1;UPDATE users SET gems = gems+100 WHERE id=2; ROLLBACK TO SAVEPOINT point1;UPDATE users SET gems = gems+100 WHERE id=3;COMMIT;

October 27, 2016 - The savepoint remains valid and can be rolled back to again later, if needed. ROLLBACK TO SAVEPOINT implicitly destroys all savepoints that were established after the named savepoint.

November 10, 2022 - The savepoint remains valid and can be rolled back to again later, if needed. ROLLBACK TO SAVEPOINT implicitly destroys all savepoints that were established after the named savepoint.

September 4, 2025 - BEGIN; -- Step 1: safe operations INSERT INTO employees (name, department) VALUES ('Alice', 'Engineering'); SAVEPOINT sp_batch; -- Step 2: risky operations INSERT INTO employees (name, department) VALUES ('Bob', 'Marketing'); -- Oops, Bob is actually in Sales -- Roll back only the risky step ROLLBACK TO SAVEPOINT sp_batch; -- Step 3: continue with corrected operation INSERT INTO employees (name, department) VALUES ('Bob', 'Sales'); COMMIT;

August 14, 2025 - The savepoint remains valid and can be rolled back to again later, if needed. ROLLBACK TO SAVEPOINT implicitly destroys all savepoints that were established after the named savepoint.

December 5, 2011 - The savepoint remains valid and can be rolled back to again later, if needed. ROLLBACK TO SAVEPOINT implicitly destroys all savepoints that were established after the named savepoint.

PostgreSQL documentation PostgreSQL feature matrix PostgreSQL versioning policy PostgreSQL latest versions @pgpedia.info (Bluesky) ... ROLLBACK TO SAVEPOINT is a transaction command for rolling back a transaction to a previously defined savepoint.

November 9, 2023 - The savepoint remains valid and can be rolled back to again later, if needed. ROLLBACK TO SAVEPOINT implicitly destroys all savepoints that were established after the named savepoint.

August 12, 2021 - The savepoint remains valid and can be rolled back to again later, if needed. ROLLBACK TO SAVEPOINT implicitly destroys all savepoints that were established after the named savepoint.

February 13, 2020 - The name to give to the new savepoint. Use ROLLBACK TO SAVEPOINT to rollback to a savepoint.

May 14, 2026 - When the statement attempting to insert value 4 generates an error, the insertion of 2 and 4 are lost because they are in the same, now-rolled back savepoint, and value 3 is in the same transaction context. The application can now only choose one of these two commands, since all other commands will be ignored: ... Choosing ROLLBACK will abort everything, including value 1, whereas ROLLBACK TO SAVEPOINT sp1 will retain value 1 and allow the transaction to continue.

INSERT ....; SAVEPOINT foo; UPDATE ....; ROLLBACK TO SAVEPOINT foo, postgresql.org/docs/8.1/static/sql-savepoint.html, or you forgot to specify programming language

Roll back all commands that were executed after the savepoint was set. The savepoint remains valid and you can roll back to it again if you need to. ROLLBACK TO SAVEPOINT destroys all savepoints that were established after the named savepoint.