Received: from sss.pgh.pa.us (sss.pgh.pa.us [209.114.132.154])
	by mail.postgresql.org (8.11.1/8.11.1) with ESMTP id f13LNqx17213
	for <pgsql-admin@postgresql.org>; Sat, 3 Feb 2001 16:23:52 -0500 (EST)
	(envelope-from tgl@sss.pgh.pa.us)
Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1])
	by sss.pgh.pa.us (8.11.1/8.11.1) with ESMTP id f13LNm904172;
	Sat, 3 Feb 2001 16:23:48 -0500 (EST)
To: "Robin's Postgres List Archive" <pglist@mail.robin.net>
cc: pgsql-admin@postgresql.org
Subject: Re: Data Corruption? 
In-reply-to: <Pine.LNX.3.96.1010202150001.18157A-100000@mail.robin.net> 
References: <Pine.LNX.3.96.1010202150001.18157A-100000@mail.robin.net>
Comments: In-reply-to "Robin's Postgres List Archive" <pglist@mail.robin.net>
	message dated "Fri, 02 Feb 2001 15:22:22 -0700"
Date: Sat, 03 Feb 2001 16:23:48 -0500
Message-ID: <4169.981235428@sss.pgh.pa.us>
From: Tom Lane <tgl@sss.pgh.pa.us>
X-Archive-Number: 200102/13
X-Sequence-Number: 613

"Robin's Postgres List Archive" <pglist@mail.robin.net> writes:
> Last month, I started getting various inexplicable error messages both
> with the web app and with psql.

I'd recommend an update to 7.0.3.  It's unlikely you'll find anyone
who's seriously interested in pursuing bugs in 6.5.2 ...

			regards, tom lane