operators.  Should report the declared oprresult type, not the return type
of the underlying proc, which might be only binary-compatible (cf.
textcat entries).

used inside fk constraints, since some of the checks
in the trigger did a SELECT oid.  Since the oid wasn't
actually used, I changed this to SELECT 1.  My test
case with non-oid tables now works and fk regression
appears to run fine on my machine.

Stephan Szabo

postmaster log with elog(DEBUG) so that they will be timestamped etc.
Once upon a time I think elog() was unsafe here, but it shouldn't be anymore.

Brent Verner, with review and kibitzing from Tom Lane.

to apply the proper Datum conversion macros to search key values.

Per report from Bernd Tegge, 10-Nov-01.

clauses per path key.  Indeed, we *must* do so or we will be unable to
form a valid plan for FULL JOIN with overlapping join conditions, eg
select * from a full join b on
a.v1 = b.v1 and a.v2 = b.v2 and a.v1 = b.v2.

Denis A Ustimenko

mergeclauses in RIGHT/FULL join cases, just like the other routines have.
I'm not quite sure why I thought it didn't need one --- but Nick
Fankhauser's recent bug report proves that it does.

This seems to fix the trouble with PowerBuilder
reported by Magbus Weber.

a NULL pointer.  Per report from Stephen Pillinger 8-Nov-01.

is gone, usage messages now go through elog(DEBUG).

per suggestion from Peter.

though alas not as unquoted function names.  De-reserve a bunch of
keywords that could have been in ColId rather than ColLabel all along.
Per recent proposal in pgsql-patches.

lists, bibliography, index, page numbering.  Add comments.

because the result looks to "scary" otherwise.