|
8 | 8 | * |
9 | 9 | * |
10 | 10 | * IDENTIFICATION |
11 | | - * $PostgreSQL: pgsql/src/backend/access/hash/hashpage.c,v 1.63 2007/01/05 22:19:22 momjian Exp $ |
| 11 | + * $PostgreSQL: pgsql/src/backend/access/hash/hashpage.c,v 1.64 2007/01/29 23:22:59 tgl Exp $ |
12 | 12 | * |
13 | 13 | * NOTES |
14 | 14 | * Postgres hash pages look like ordinary relation pages. The opaque |
@@ -275,6 +275,11 @@ _hash_metapinit(Relation rel) |
275 | 275 | metap->hashm_bmshift=i+BYTE_TO_BIT; |
276 | 276 | Assert((1 <<BMPG_SHIFT(metap))== (BMPG_MASK(metap)+1)); |
277 | 277 |
|
| 278 | +/* |
| 279 | + * Label the index with its primary hash support function's OID. This is |
| 280 | + * pretty useless for normal operation (in fact, hashm_procid is not used |
| 281 | + * anywhere), but it might be handy for forensic purposes so we keep it. |
| 282 | + */ |
278 | 283 | metap->hashm_procid=index_getprocid(rel,1,HASHPROC); |
279 | 284 |
|
280 | 285 | /* |
|