aboutsummaryrefslogtreecommitdiff
path: root/src/backend/commands/cluster.c
diff options
context:
space:
mode:
authorTom Lane <tgl@sss.pgh.pa.us>2007-09-11 17:15:55 +0000
committerTom Lane <tgl@sss.pgh.pa.us>2007-09-11 17:15:55 +0000
commit371b213929e2723a6d00db040653927710e4ad6a (patch)
tree755766d5df4dd53cc8bafa49070a5c78e1595314 /src/backend/commands/cluster.c
parent13ad48eb8a49bbba4e13026ed69f07a51d52d244 (diff)
downloadpostgresql-371b213929e2723a6d00db040653927710e4ad6a.tar.gz
postgresql-371b213929e2723a6d00db040653927710e4ad6a.zip
Make sure that open hash table scans are cleaned up when bgwriter tries to
recover from elog(ERROR). Problem was created by introduction of hash seq search tracking awhile back, and affects all branches that have bgwriter; in HEAD the disease has snuck into autovacuum and walwriter too. (Not sure that the latter two use hash_seq_search at the moment, but surely they might someday.) Per report from Sergey Koposov.
Diffstat (limited to 'src/backend/commands/cluster.c')
0 files changed, 0 insertions, 0 deletions