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 eA2HHbl40435 for ; Thu, 2 Nov 2000 12:17:37 -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 eA2HH5525784; Thu, 2 Nov 2000 12:17:05 -0500 (EST) To: "pgsql-sql" cc: zakkr@zf.jcu.cz, tjk@tksoft.com, pgsql-sql@postgresql.org Subject: Re: Re(2): Re(2): Large Object dump ? In-reply-to: References: Comments: In-reply-to "pgsql-sql" message dated "Wed, 01 Nov 2000 21:44:50 +0800" Date: Thu, 02 Nov 2000 12:17:05 -0500 Message-ID: <25781.973185425@sss.pgh.pa.us> From: Tom Lane X-Archive-Number: 200011/16 X-Sequence-Number: 47 "pgsql-sql" writes: > Exported 1131 large objects. > NOTICE: LockReleaseAll: xid loop detected, giving up Pre-7.0 LockReleaseAll() contained an entirely arbitrary assumption that it should never encounter a situation where there were more than 1000 locks held by one transaction :-(. So it chokes when you access more than 1000 LOs in the same transaction. Dunno about your other issue, but clearly your application is failing to report whatever error message was returned when the transaction was aborted... regards, tom lane