mirror of
https://git.postgresql.org/git/postgresql.git
synced 2025-01-12 18:34:36 +08:00
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.
This commit is contained in:
parent
7176065273
commit
b58dba7976
@ -37,7 +37,7 @@
|
||||
*
|
||||
*
|
||||
* IDENTIFICATION
|
||||
* $PostgreSQL: pgsql/src/backend/postmaster/bgwriter.c,v 1.33.2.1 2007/01/27 20:15:47 tgl Exp $
|
||||
* $PostgreSQL: pgsql/src/backend/postmaster/bgwriter.c,v 1.33.2.2 2007/09/11 17:15:40 tgl Exp $
|
||||
*
|
||||
*-------------------------------------------------------------------------
|
||||
*/
|
||||
@ -273,6 +273,7 @@ BackgroundWriterMain(void)
|
||||
/* we needn't bother with the other ResourceOwnerRelease phases */
|
||||
AtEOXact_Buffers(false);
|
||||
AtEOXact_Files();
|
||||
AtEOXact_HashTables(false);
|
||||
|
||||
/* Warn any waiting backends that the checkpoint failed. */
|
||||
if (ckpt_active)
|
||||
|
Loading…
Reference in New Issue
Block a user