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

Making use of snapshot too old

VACUUM is doing a good job and it will reclaim free space as needed. But when can VACUUM actually clean out rows and turn them into free space? The rule is this: if a row cannot be seen by anybody anymore, it can be reclaimed. In reality this means that everything that is no longer seen even by the oldest transaction can be considered to be really dead.

This also implies that really long transactions can postpone cleanup for quite some time. The logical consequence is table bloat. Tables will grow beyond proportion and performance will tend to go downhill.

Fortunately PostgreSQL 9.6 has a nice feature that allows the administrator to intelligently limit the duration of a transaction. Oracle administrators will be familiar with the snapshot too old error; since PostgreSQL 9.6, this error message is also available. But it is more of a feature than an unintended side-effect of bad configuration (which it actually is in Oracle).

To limit the lifetime of snapshots, you can make use of a setting in postgresql.conf:

old_snapshot_threshold = -1             
# 1min-60d; -1 disables; 0 is immediate

If this variable is set, transactions will fail after a certain amount of time. Note that this setting is on an instance level and it cannot be set inside a session. By limiting the size of a transaction, the risk of insanely long transactions will decrease drastically.

主站蜘蛛池模板: 奉新县| 天峻县| 湟中县| 镇沅| 同江市| 宁南县| 曲沃县| 阳原县| 富顺县| 石林| 区。| 水城县| 信阳市| 麻城市| 四平市| 博湖县| 壶关县| 固镇县| 保康县| 敖汉旗| 余姚市| 玉龙| 筠连县| 湖南省| 峡江县| 满城县| 二连浩特市| 张掖市| 平遥县| 苗栗县| 淳化县| 玉屏| 巴楚县| 吐鲁番市| 江川县| 慈利县| 大厂| 灌云县| 盱眙县| 修武县| 南京市|