more on recycled trans log death

i just ran into this problem yesterday. i read thru the past postings on
this scenario. one thing that i noticed that i didn't see in the previous
posts is that i only get this when i have psql connected to the specific
db that i'm inserting to.

if i had psql connected, i'd get ~50000 inserts at most before i saw a log
recycle and crash. once, i noticed the psql correlation, i shut it down
and tested a few time. everything seemed to work fine. i've had my
insert script running for about 10hrs now. it's done a million inserts
and recycled log files named from 0x05 to 0x23.

this could be a coincident. i haven't looked at the source yet. (and
probably won't have time to). but i hope this gives some insight.

phil