|
1 | | -<!-- $PostgreSQL: pgsql/doc/src/sgml/release.sgml,v 1.532 2007/10/25 02:50:26 momjian Exp $ --> |
| 1 | +<!-- $PostgreSQL: pgsql/doc/src/sgml/release.sgml,v 1.533 2007/11/01 22:38:36 momjian Exp $ --> |
2 | 2 | <!-- |
3 | 3 |
|
4 | 4 | Typical markup: |
@@ -450,6 +450,18 @@ do it for earlier branch release files. |
450 | 450 | </para> |
451 | 451 | </listitem> |
452 | 452 |
|
| 453 | + <listitem> |
| 454 | + <para> |
| 455 | + Internal hashing functions are now more uniformly-distributed (Tom) |
| 456 | + </para> |
| 457 | + |
| 458 | + <para> |
| 459 | + If application code was calling and storing hash values using |
| 460 | + internal <productname>PostgreSQL</> hashing functions, the hash |
| 461 | + values must be regenerated. |
| 462 | + </para> |
| 463 | + </listitem> |
| 464 | + |
453 | 465 | <listitem> |
454 | 466 | <para> |
455 | 467 | Add C macros for handling variable-length data values (Greg |
|