> you can't do cross db queries the same way you can in SQL server
Yes, Postgres does not support cross DB queries.
> I don't really want to use the linkName.dbname.schema.table as in the past I've seen pretty bad performance
Sure, it is not performing fast in current implementation. However, there is a lot to improve. Similiarly to bulk INSERT, provider can support some kind of bulk UPDATE. We will definitely add this capability to future versions of the provider. In the mean time the most efficient way would be to use two OLEDB connections, create temp table and perform UPDATE with INNER JOIN as you said. For inserting large number of rows you can use COPY since it is very fast in Postgres. We are adding COPY support into provider now, so it will be available soon.
> When I am doing an insert query, and click parse query, BID's crashes.
I cannot reproduce it in build 2096. Could you try it with www.pgoledb.com/downloads/PGNP32-184.108.40.2066.exe
and send us the insert statement if it still crashes?
> we can't seem to perform a multiple statement query in the SQL task
Let me experiment with this. I'll let you know.