@@ -364,15 +364,10 @@ The sequence will remain in the database until explicitly dropped using
364364</caution>
365365 </para>
366366
367- <para>
368- The <firstterm>exact numerics</firstterm> <type>decimal</type> and
369- <type>numeric</type>
370- have fully implemented syntax but currently
371- (<productname>Postgres</productname> v6.4)
372- support only a small range of precision and/or range values.
373- The <type>int8</type> type may not be available on all platforms since
374- it relies on compiler support for this.
375- </para>
367+ <para>
368+ The <type>int8</type> type may not be available on all platforms since
369+ it relies on compiler support for this.
370+ </para>
376371
377372</sect1>
378373
@@ -412,14 +407,10 @@ then the money type should use the monetary conventions defined for
412407</table>
413408</para>
414409
415- <para>
416- <type>numeric</type>
417- should eventually replace the money type. It has a
418- fully implemented syntax but currently
419- (<productname>Postgres</productname> v6.4)
420- support only a small range of precision and/or range values
421- and cannot adequately substitute for the money type.
422- </para>
410+ <para>
411+ <type>numeric</type>
412+ will replace the money type, and should be preferred.
413+ </para>
423414
424415</sect1>
425416
