pgsql: Make sure that open hash table scans are cleaned up when bgwriter

From: tgl(at)postgresql(dot)org (Tom Lane)
To: pgsql-committers(at)postgresql(dot)org
Subject: pgsql: Make sure that open hash table scans are cleaned up when bgwriter
Date: 2007-09-11 17:15:48
Message-ID: 20070911171548.1F772754206@cvs.postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers

Log Message:
-----------
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.

Tags:
----
REL8_1_STABLE

Modified Files:
--------------
pgsql/src/backend/postmaster:
bgwriter.c (r1.21.2.2 -> r1.21.2.3)
(http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/postmaster/bgwriter.c?r1=1.21.2.2&r2=1.21.2.3)

Browse pgsql-committers by date

  From Date Subject
Next Message Tom Lane 2007-09-11 17:15:55 pgsql: Make sure that open hash table scans are cleaned up when bgwriter
Previous Message Tom Lane 2007-09-11 17:15:40 pgsql: Make sure that open hash table scans are cleaned up when bgwriter