官术网_书友最值得收藏!

Making use of savepoints

In professional applications, it can be pretty hard to write reasonably long transactions without ever encountering a single error. To solve the problem, users can utilize something called SAVEPOINT. As the name indicates, it is a safe place inside a transaction that the application can return to in the event things go terribly wrong. Here is an example:

test=# BEGIN; 
BEGIN
test=# SELECT 1;
?column?
----------
1
(1 row)

test=# SAVEPOINT a;
SAVEPOINT
test=# SELECT 2 / 0;
ERROR: division by zero
test=# ROLLBACK TO SAVEPOINT a;
ROLLBACK
test=# SELECT 3;
?column?
----------
3
(1 row)

test=# COMMIT;
COMMIT

After the first SELECT clause, I decided to create a SAVEPOINT to make sure that the application can always return to this point inside the transaction. As you can see, a SAVEPOINT has a name, which is referred to later.

After returning to a, the transaction can proceed normally. The code has jumped back before the error, so everything is fine.

The number of savepoints inside a transaction is practically unlimited. We have seen customers with over 250,000 savepoints in a single operation. PostgreSQL can easily handle that.

If you want to remove a savepoint from inside a transaction, there is RELEASE SAVEPOINT:

test=# h RELEASE SAVEPOINT  
Command: RELEASE SAVEPOINT
Description: destroy a previously defined savepoint
Syntax:
RELEASE [ SAVEPOINT ] savepoint_name

Many people ask, What will happen if you try to reach a savepoint after a transaction has ended? The answer is that the life of a savepoint ends as soon as the transaction ends. In other words, there is no way to return to a certain point in time after the transactions have been completed.

主站蜘蛛池模板: 枣阳市| 青冈县| 北海市| 顺平县| 余江县| 莱西市| 利辛县| 白沙| 山阳县| 陇川县| 大冶市| 乐清市| 扶风县| 淄博市| 临洮县| 长丰县| 集安市| 平塘县| 桐乡市| 安龙县| 成安县| 自贡市| 库尔勒市| 松溪县| 绍兴县| 英德市| 米林县| 太湖县| 新建县| 平原县| 乐至县| 鲜城| 嵊州市| 嘉定区| 泉州市| 武清区| 左云县| 苏尼特左旗| 和政县| 柞水县| 涟源市|