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

  • Mastering PostgreSQL 9.6
  • Hans Jurgen Schonig
  • 279字
  • 2021-07-09 19:57:11

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.

主站蜘蛛池模板: 吐鲁番市| 三都| 日照市| 抚州市| 大厂| 乌拉特后旗| 灌阳县| 黔西| 红原县| 昌江| 大方县| 桂林市| 米易县| 堆龙德庆县| 阿克| 开江县| 吉林市| 运城市| 武陟县| 云和县| 叙永县| 碌曲县| 霞浦县| 老河口市| 南投县| 休宁县| 光山县| 增城市| 桑植县| 青州市| 六安市| 红河县| 淳化县| 赤壁市| 兰西县| 闽清县| 白城市| 托里县| 昌乐县| 鹿邑县| 侯马市|