Commit914ae8d

committed

Adjust outdated comment.

Commit5dfc198 removed the onlyexisting caller of hash_freeze, but left behind a comment indicatingthat hash_freeze was still used. Adjust.Kyotaro HoriguchiDiscussion:http://postgr.es/m/20170424.165541.230634914.horiguchi.kyotaro@lab.ntt.co.jp

1 parent7cc14ae commit914ae8dCopy full SHA for 914ae8d

File tree

-3

lines changed

-3

lines changed

Lines changed: 1 addition & 3 deletions

Original file line number	Diff line number	Diff line change
`@@ -1330,9 +1330,7 @@ hash_get_num_entries(HTAB *hashp)`
`1330`	`1330`	`*`
`1331`	`1331`	`* NOTE: it is possible to use hash_seq_init/hash_seq_search without any`
`1332`	`1332`	`* worry about hash_seq_term cleanup, if the hashtable is first locked against`
`1333`		`- * further insertions by calling hash_freeze. This is used by nodeAgg.c,`
`1334`		`- * wherein it is inconvenient to track whether a scan is still open, and`
`1335`		`- * there's no possibility of further insertions after readout has begun.`
	`1333`	`+ * further insertions by calling hash_freeze.`
`1336`	`1334`	`*`
`1337`	`1335`	`* NOTE: to use this with a partitioned hashtable, caller had better hold`
`1338`	`1336`	`* at least shared lock on all partitions of the table throughout the scan!`

Comments

(0)