>>to change the README in contrib/dblink?
>>
>
> No, I don't think that's a problem.  Send a patch.
>

Here's a (documentation only) patch for the contrib/dblink README.

Joe Conway

tag it as b4, with all the changes that have gone on ...

requests for implicit trivial coercions.  Prevents sillinesses like
this one:
regression=# select x.int8_tbl.q1 from int8_tbl x;
ERROR:  fmgr_info: function 270997776: cache lookup failed

wasn't updated to handle more than two decimal digits for fractional seconds
that now are possible in 7.2.  This patch fixes the timestamp parsing logic.
I have built and tested on both jdbc1 and jdbc2.

to be used, causing extra sql statements to be executed.  This was a
significant performance problem with the database meta data classes.
The fix is a simple one liner.

object.  This should prevent the compiler from reordering loads and stores
into or out of a critical section.

per complaint from Kemin Zhou.
Fix lack of precision in numeric stddev/variance.

set-returning functions in its target list.  This ensures that we
won't rewrite the query in a way that places set-returning functions
into quals (WHERE clauses).  Cf. bug reports from Joe Conway.

reordering operations at its whim.  Releasing TAS lock before we've
finished updating proc structure is uncool.

From Manuel Sugawara, approved by Karel Zak.

 DSL line at home broke things right in the middle of an update. :(

 parens. This is not SQL spec syntax, so later we will remove
 this extension from gram.y.

 between Postgres and PostgreSQL.

Mention SQL9x precision syntax for date/time types.
Use PostgreSQL consistantly throughout docs. Before, usage was split evenly
 between Postgres and PostgreSQL.