mirror of
https://github.com/postgres/postgres.git
synced 2025-05-02 11:44:50 +03:00
Adjust outdated comment.
Commit 5dfc198146b49ce7ecc8a1fc9d5e171fb75f6ba5 removed the only existing caller of hash_freeze, but left behind a comment indicating that hash_freeze was still used. Adjust. Kyotaro Horiguchi Discussion: http://postgr.es/m/20170424.165541.230634914.horiguchi.kyotaro@lab.ntt.co.jp
This commit is contained in:
parent
7cc14ae9d8
commit
914ae8d3cb
@ -1330,9 +1330,7 @@ hash_get_num_entries(HTAB *hashp)
|
|||||||
*
|
*
|
||||||
* NOTE: it is possible to use hash_seq_init/hash_seq_search without any
|
* NOTE: it is possible to use hash_seq_init/hash_seq_search without any
|
||||||
* worry about hash_seq_term cleanup, if the hashtable is first locked against
|
* worry about hash_seq_term cleanup, if the hashtable is first locked against
|
||||||
* further insertions by calling hash_freeze. This is used by nodeAgg.c,
|
* further insertions by calling hash_freeze.
|
||||||
* wherein it is inconvenient to track whether a scan is still open, and
|
|
||||||
* there's no possibility of further insertions after readout has begun.
|
|
||||||
*
|
*
|
||||||
* NOTE: to use this with a partitioned hashtable, caller had better hold
|
* NOTE: to use this with a partitioned hashtable, caller had better hold
|
||||||
* at least shared lock on all partitions of the table throughout the scan!
|
* at least shared lock on all partitions of the table throughout the scan!
|
||||||
|
Loading…
x
Reference in New Issue
Block a user