Received: from maia.hub.org (maia-2.hub.org [200.46.204.251]) by mail.postgresql.org (Postfix) with ESMTP id 9C5091337B82 for ; Wed, 4 May 2011 19:53:35 -0300 (ADT) Received: from mail.postgresql.org ([200.46.204.86]) by maia.hub.org (mx1.hub.org [200.46.204.251]) (amavisd-maia, port 10024) with ESMTP id 43983-04 for ; Wed, 4 May 2011 22:53:17 +0000 (UTC) X-Greylist: domain auto-whitelisted by SQLgrey-1.7.6 Received: from mail-bw0-f46.google.com (mail-bw0-f46.google.com [209.85.214.46]) by mail.postgresql.org (Postfix) with ESMTP id 1BA901337B47 for ; Wed, 4 May 2011 19:53:16 -0300 (ADT) Received: by bwz15 with SMTP id 15so1390352bwz.19 for ; Wed, 04 May 2011 15:53:16 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:date :message-id:subject:from:to:content-type:content-transfer-encoding; bh=JOisMtdS8Zx6HehL1KAEQUtPoCFrEkz07Hq7mNsu88w=; b=wn9hNU6GZ9TmQpT5ydeZNOktLFo5QgQnNS7ZX3uS+TSpLk2GFQlKjaiGt2tfMgO202 IMqH0SuRt0kh0Fti93n3M5zWiw5wzVIfMcQtmB1+oJcQjyPbCc5JPixwdMvTdyAYKVWI 4fETGiWegpB/yd/Zhq26jL32TnbXzAoHGYQS4= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type:content-transfer-encoding; b=nY9Pf4CQWvAWr2grcc7gxTIpPBQxBoQBfHOhwFZLyPY2yQ0hJrJmvLazPQlo1kQ/dV p9Il3hdVpZU7hPw9i89sgY2n2FvTrHlEESAEoM+PT3FuIkDuEoe8mInuYzXoAjyRHhBo MZQ6Nl9r6kGDajklJSCzQJG3mPQuu5OMiWZT0= MIME-Version: 1.0 Received: by 10.204.14.144 with SMTP id g16mr1673029bka.34.1304549596202; Wed, 04 May 2011 15:53:16 -0700 (PDT) Received: by 10.204.14.195 with HTTP; Wed, 4 May 2011 15:53:16 -0700 (PDT) In-Reply-To: References: <4DBFB066.9010202@orkash.com> Date: Thu, 5 May 2011 08:23:16 +0930 Message-ID: Subject: Re: Unable to Insert Row From: Sam Stearns To: pgsql-admin@postgresql.org Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=-1.888 tagged_above=-10 required=5 tests=BAYES_00=-1.9, FREEMAIL_FROM=0.001, RFC_ABUSE_POST=0.001, T_TO_NO_BRKTS_FREEMAIL=0.01 X-Spam-Level: X-Archive-Number: 201105/55 X-Sequence-Number: 37492 Dump/restore of table resolved this problem. On Wed, May 4, 2011 at 8:22 AM, Sam Stearns wrote: > Does anyone else have any ideas on how to solve this problem besides > this mysterious repair command? > > On Tue, May 3, 2011 at 6:33 PM, Sam Stearns wrote= : >> ---------- Forwarded message ---------- >> From: Sam Stearns >> Date: Tue, May 3, 2011 at 6:32 PM >> Subject: Re: [ADMIN] Unable to Insert Row >> To: Adarsh Sharma >> >> >> Thanks, Adarsh. >> >> I don't see any references to a repair command in the 8.3 doco. >> >> On Tue, May 3, 2011 at 5:06 PM, Adarsh Sharma = wrote: >>> Try again after repairing the tables with the repair command. >>> >>> Best Regards, >>> Adarsh >>> >>> Sam Stearns wrote: >>>> >>>> Howdy, >>>> >>>> Environment: >>>> >>>> Postgres 8.3.14 >>>> Solaris 10 >>>> >>>> When attempting to insert a row, the following error is received: >>>> >>>> ERROR: =A0could not open relation with OID 926167091 >>>> >>>> This OID does not exist anywhere in the database. =A0Most inserts on >>>> this table are successful. =A0It is only for 2 particular id's where t= he >>>> inserts are failing with this error. =A0The id column is indexed. =A0I >>>> have tried vacuum analyzing the database. =A0Still get the error. =A0I >>>> have NOT tried re-indexing yet. =A0Some googling says a restart of >>>> postgres fixes it. =A0I would like to get your thoughts first 'though, >>>> please. >>>> >>>> Thank you, >>>> >>>> Sam >>>> >>>> >>> >>> >> >