Received: from sss2.sss.pgh.pa.us (sss.pgh.pa.us [209.114.166.2])
	by hub.org (8.9.3/8.9.3) with ESMTP id KAA45979
	for <pgsql-interfaces@postgresql.org>;
	Mon, 8 May 2000 10:09:01 -0400 (EDT)
	(envelope-from tgl@sss.pgh.pa.us)
Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1])
	by sss2.sss.pgh.pa.us (8.9.3/8.9.3) with ESMTP id KAA01532;
	Mon, 8 May 2000 10:08:58 -0400 (EDT)
To: "Oscar Serrano" <oserra@fondos.net>
cc: pgsql-interfaces@postgresql.org
Subject: Re: postgres crash. HELP 
In-reply-to: <NDBBKNFDELOHICEHIMGGGEFLCDAA.oserra@fondos.net> 
References: <NDBBKNFDELOHICEHIMGGGEFLCDAA.oserra@fondos.net>
Comments: In-reply-to "Oscar Serrano" <oserra@fondos.net>
	message dated "Mon, 08 May 2000 11:11:54 +0200"
Date: Mon, 08 May 2000 10:08:58 -0400
Message-ID: <1529.957794938@sss.pgh.pa.us>
From: Tom Lane <tgl@sss.pgh.pa.us>
X-Archive-Number: 200005/70

"Oscar Serrano" <oserra@fondos.net> writes:
> I had a backup fortunately. I first had to make some pg_dump of some tables
> that were not corrupted and restore them later.
> I have postgres 6.5.3.
> I didn't know about pg_upgrade. I will have to read about it.
> Actually I have my dabatases open to every IP address, so anybody that
> enters our web page, and visits some of our applets, the connect via JDBC to
> our database. I think that during one of this connection, the postgres
> crashed. I'm going to stop using JDBC.
> Is there any known problem with the ODBC of the postgres?

I don't think you can fairly blame JDBC for this problem; it's an
internal-to-the-backend bug of some sort.  I would suggest upgrading
to 7.0 as a more reasonable response... we've fixed an awful lot of
bugs since 6.5.*.

			regards, tom lane