Re: Database handle destroyed without explicit disconnect

"Susan Lane" <suel@dpn.com> writes:
> I ran the script and after it told me that it was creating my sequences, it
> said "Database handle destroyed without explicit disconnect".

That might be normal behavior for that script; I can't tell without an
Oracle installation to try it against, but it does look like it exits
without bothering to close the Oracle DBI connection.  That wouldn't
affect Postgres, however, especially considering that ora2pl never
contacts the Postgres database at all.  (AFAICT, it just writes a script
file that you are supposed to feed to Postgres afterwards.  Did you
actually do so?)

> Now when I go
> into psql, any command I try (even /?) gives me a segmentation fault.

*Any* command?  That's hard to believe.  What different commands have you
tried?  There was a bug in a recent psql version (7.1.1 I believe) that
would make it dump core after certain single-letter backslash commands,
but I can't tell if that's what your problem is.

> Pgadmin tells me when I try to drop my database that I can't drop an open
> database.

Normal behavior, if that's what you tried to do.

> My log tells me "pq_recvbuf: unexpected EOF on client connection".

This is not evidence of a catastrophe either.  So far I suspect that
you've had the bad luck to trip over a small bug in the prior release
of psql, but I can't tell that anything else is wrong.

            regards, tom lane