On 14/05/2008, at 10:31 PM, Paul Hoadley wrote:
Aside from that, this DOES seem odd -- I don't see this behavior at all. I don't know what version of the PG plugin you're using, but I would tend to always say "yes" to getting the latest. However, I did commit just now a defensive closing of any connection that was left open after we run our operations (this will be in tonight's nightly build). Previously I was only closing the one that we explicitly opened, but it looks like EOF is opening some additional ones for some reason.
I will upgrade WO and the plug-in and re-test.
OK, WO 5.4.1, PostgresqlPlugIn 4.0.0.665. After _executing_ the SQL, I get this:
AM3=# SELECT datname,procpid,current_query FROM pg_stat_activity ORDER BY procpid ;
datname | procpid | current_query
---------+---------+-------------------------------------------------------------------------------
AM3 | 11977 | SELECT datname,procpid,current_query FROM pg_stat_activity ORDER BY procpid ;
AM3 | 11980 | <IDLE> in transaction
AM3 | 11994 | <IDLE>
AM3 | 12024 | <IDLE>
AM3 | 12055 | <IDLE>
AM3 | 12056 | <IDLE>
AM3 | 12057 | <IDLE>
AM3 | 12058 | <IDLE>
AM3 | 12059 | <IDLE>
AM3 | 12060 | <IDLE>
AM3 | 12061 | <IDLE>
AM3 | 12062 | <IDLE>
AM3 | 12063 | <IDLE>
AM3 | 12064 | <IDLE>
AM3 | 12065 | <IDLE>
AM3 | 12066 | <IDLE>
AM3 | 12067 | <IDLE>
AM3 | 12068 | <IDLE>
AM3 | 12069 | <IDLE>
AM3 | 12070 | <IDLE>
AM3 | 12071 | <IDLE>
AM3 | 12072 | <IDLE>
AM3 | 12073 | <IDLE>
AM3 | 12074 | <IDLE>
AM3 | 12075 | <IDLE>
AM3 | 12076 | <IDLE>
AM3 | 12077 | <IDLE>
(27 rows)
On the upside, I didn't get any of the usual one-per-table error dialogs about the non-existent EOF_TMP_TABLEs. I'll try the new build of the plug-in tomorrow.