X-Original-To: pgsql-admin-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.144]) by svr1.postgresql.org (Postfix) with ESMTP id 72EA63A639B; Sat, 11 Dec 2004 18:27:33 +0000 (GMT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 05997-03; Sat, 11 Dec 2004 18:27:29 +0000 (GMT) Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130]) by svr1.postgresql.org (Postfix) with ESMTP id 22EDA3A644E; Sat, 11 Dec 2004 18:27:28 +0000 (GMT) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.13.1/8.13.1) with ESMTP id iBBIRLYV017798; Sat, 11 Dec 2004 13:27:22 -0500 (EST) To: cjwhite@cisco.com Cc: pgsql-admin@postgresql.org, pgsql-jdbc@postgresql.org Subject: Re: [JDBC] Issue with large objects In-reply-to: <200412111742.iBBHgF6n015475@sj-core-3.cisco.com> References: <200412111742.iBBHgF6n015475@sj-core-3.cisco.com> Comments: In-reply-to "Chris White (cjwhite)" message dated "Sat, 11 Dec 2004 09:42:15 -0800" Date: Sat, 11 Dec 2004 13:27:21 -0500 Message-ID: <17797.1102789641@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0.006 tagged_above=0 required=5 tests=AWL X-Spam-Level: X-Archive-Number: 200412/100 X-Sequence-Number: 15686 "Chris White (cjwhite)" writes: > Also, I found by re-indexing the pg_largeobject table the problem seems to > have gone away. Um. That's probably destroyed the evidence :-( ie gotten rid of whatever weird state you'd gotten the index into. But if you have any luck reproducing it, I definitely want to know. regards, tom lane