summaryrefslogtreecommitdiff
path: root/src/backend/access/gist/gist.c
diff options
context:
space:
mode:
authorTom Lane <tgl@sss.pgh.pa.us>2007-09-11 17:15:33 +0000
committerTom Lane <tgl@sss.pgh.pa.us>2007-09-11 17:15:33 +0000
commitf181f9e1e49b1546d7e42b43a04487dfc6f73690 (patch)
tree7f62f2fb4cdc5506c03cb3c069e7075a1a1d755e /src/backend/access/gist/gist.c
parent5cf785a4de1fd393983da8888ae0ece3a0945e9c (diff)
downloadpostgresql-f181f9e1e49b1546d7e42b43a04487dfc6f73690.tar.gz
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/access/gist/gist.c')
0 files changed, 0 insertions, 0 deletions