Received: from maia.hub.org (maia-3.hub.org [200.46.204.243]) by mail.postgresql.org (Postfix) with ESMTP id C1B621337BF8 for ; Tue, 3 May 2011 19:59:04 -0300 (ADT) Received: from mail.postgresql.org ([200.46.204.86]) by maia.hub.org (mx1.hub.org [200.46.204.243]) (amavisd-maia, port 10024) with ESMTP id 45772-01-3 for ; Tue, 3 May 2011 22:58:57 +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 1BC751337C70 for ; Tue, 3 May 2011 19:53:25 -0300 (ADT) Received: by bwz15 with SMTP id 15so525339bwz.19 for ; Tue, 03 May 2011 15:53:25 -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=lyGdgzyXICXR6s6o96ltNWc9SzldADKPwMQvnLoV5t0=; b=esWPl3Q4z2HZQP42JextRwjM22HldpnM2si4YOxCav+iB4A2TxCUmOfjt71AAj//xH dhiYyA9Kp3t6vaHhsOpR0hW5fz/HK1bXAzL4ZH27T7cqLcxrGC+KybHoifo5gjPQHPJE UeipxfM0wRALIaosuP+cODEyzdR4VV+JdbLXY= 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=Y5237oYH3YXNrmP9PfUHyLFbH0T1VkMJB8PUKfIa860KiqtamwdCErGF2aLEX95WOc 49e8tIdfMpflrm6cHIetIm24MrrZKGn9323pBH4453+i/YMTK/YS/+CJke+gw+VYZ3xr Qb5MNhfDFE0L9ddh5xDqIUM8bwIxBbePMxqcQ= MIME-Version: 1.0 Received: by 10.204.116.134 with SMTP id m6mr411623bkq.7.1304463126403; Tue, 03 May 2011 15:52:06 -0700 (PDT) Received: by 10.204.14.195 with HTTP; Tue, 3 May 2011 15:52:06 -0700 (PDT) In-Reply-To: References: <4DBFB066.9010202@orkash.com> Date: Wed, 4 May 2011 08:22:06 +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/34 X-Sequence-Number: 37471 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 th= e >>> 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 >>> >>> >> >> >