database/postgres
1
0
Fork 0
mirror of https://github.com/postgres/postgres.git synced 2025-07-28 23:42:10 +03:00
Code Activity

Adjust outdated comment.

Browse Source 
Commit 5dfc198146 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:
Robert Haas
2017-04-25 10:57:13 -04:00
parent 7cc14ae9d8
commit 914ae8d3cb
1 changed files with 1 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
src/backend/utils/hash/dynahash.c
View File

@ -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!