Re: Unable to Insert Row - Mailing list pgsql-admin

From Sam Stearns
Subject Re: Unable to Insert Row
Date
Msg-id BANLkTimE7yAxD-qnUQ0gLhbKc2tN3Mp2vA@mail.gmail.com
Whole thread Raw
In response to Re: Unable to Insert Row  (Sam Stearns <samtstearns@gmail.com>)
Responses Re: Unable to Insert Row
List pgsql-admin
Dump/restore of table resolved this problem.

On Wed, May 4, 2011 at 8:22 AM, Sam Stearns <samtstearns@gmail.com> 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 <samtstearns@gmail.com> wrote:
>> ---------- Forwarded message ----------
>> From: Sam Stearns <samtstearns@gmail.com>
>> Date: Tue, May 3, 2011 at 6:32 PM
>> Subject: Re: [ADMIN] Unable to Insert Row
>> To: Adarsh Sharma <adarsh.sharma@orkash.com>
>>
>>
>> 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 <adarsh.sharma@orkash.com> 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:  could not open relation with OID 926167091
>>>>
>>>> This OID does not exist anywhere in the database.  Most inserts on
>>>> this table are successful.  It is only for 2 particular id's where the
>>>> inserts are failing with this error.  The id column is indexed.  I
>>>> have tried vacuum analyzing the database.  Still get the error.  I
>>>> have NOT tried re-indexing yet.  Some googling says a restart of
>>>> postgres fixes it.  I would like to get your thoughts first 'though,
>>>> please.
>>>>
>>>> Thank you,
>>>>
>>>> Sam
>>>>
>>>>
>>>
>>>
>>
>

pgsql-admin by date:

Previous
From: Dinesh Bhandary
Date:
Subject: worker took too long to start; cancelled ( postgres 9.0.3)
Next
From: ktm@rice.edu
Date:
Subject: Re: Re: best practice for moving millions of rows to child table when setting up partitioning?