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 eADG2fs76638 for ; Mon, 13 Nov 2000 11:02:41 -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 eADFxKD09579; Mon, 13 Nov 2000 10:59:20 -0500 (EST) To: Gabriel Lopez cc: Peter Mount , "'dhjr@hddesign.com'" , pgsql-interfaces@postgresql.org Subject: Re: wrong documentation and others ..... In-reply-to: <3A0FDAF0.554766F6@dif.um.es> References: <1B3D5E532D18D311861A00600865478CF1B432@exchange1.nt.maidstone.gov.uk> <3A0FDAF0.554766F6@dif.um.es> Comments: In-reply-to Gabriel Lopez message dated "Mon, 13 Nov 2000 13:13:36 +0100" Date: Mon, 13 Nov 2000 10:59:20 -0500 Message-ID: <9576.974131160@sss.pgh.pa.us> From: Tom Lane X-Archive-Number: 200011/128 X-Sequence-Number: 164 Gabriel Lopez writes: > The error appear also in linux with RedHat 6.2 and postgresql 7.0.2 > I'm using the example from psql: > insert into tbl_objectshelf values > ('39',lo_import('/etc/inittab')); > when I run the example several times 50, 100, etc the exception is > thows: > FATAL 1: my bits moved right off the end of the world! > Recreate index pg_attribute_relid_attnum_index. We've heard a couple reports of this failure during large-object creation, but I've never had any luck duplicating the problem :-( regards, tom lane