"Bill Eaton" <[EMAIL PROTECTED]> writes:
> Oops. That's a detail I left out. I can only reproduce this problem so far
> in PGAdmin. I couldn't reproduce the error in psql or in a linked table in
> MSAccess.

Turn on query logging so you can see exactly what query PGAdmin is
issuing to provoke the error.  There isn't any magic in PGAdmin, it
has to issue the same queries as anyone else.

                        regards, tom lane

---------------------------(end of broadcast)---------------------------
TIP 9: In versions below 8.0, the planner will ignore your desire to
       choose an index scan if your joining column's datatypes do not
       match

Reply via email to