In an attempt to throw the authorities off his trail, johnsw@xxxxxxxxxxxxx (John Sidney-Woollett) transmitted: > MAKE SURE YOU STOP YOUR APPLICATION RUNNING AGAINST YOUR MASTER > DATABASE WHEN REMOVING THE WHOLE SLONY CLUSTER, or at least re-cycle > all your open connections after the event! > > The connections appear to "remember" or refer to objects which are > removed by the uninstall node script. And you get lots of errors as a > result (and possible data loss??)... As has been noted by others, this is an artifact of the JDBC driver holding onto a stored query plan. And it's somewhat worth noting that this is not unique to Slony-I... I have added warnings to relevant documentation in the Slony-I CVS tree. This may also be worthy of a FAQ note for PostgreSQL itself, and is almost certainly worthy of note in the JDBC documentation... -- (format nil "~S@~S" "cbbrowne" "acm.org") http://linuxdatabases.info/info/slony.html "We should start referring to processes which run in the background by their correct technical name:... paenguins." -- Kevin M Bealer ---------------------------(end of broadcast)--------------------------- TIP 6: Have you searched our list archives? http://archives.postgresql.org
