From: | Sam Stearns <samtstearns(at)gmail(dot)com> |
---|---|
To: | pgsql-admin(at)postgresql(dot)org |
Subject: | Fwd: Unable to Insert Row |
Date: | 2011-05-03 09:03:07 |
Message-ID: | BANLkTikTqXtq1+05BVmUBsb-DaVSWrBbxQ@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
---------- Forwarded message ----------
From: Sam Stearns <samtstearns(at)gmail(dot)com>
Date: Tue, May 3, 2011 at 6:32 PM
Subject: Re: [ADMIN] Unable to Insert Row
To: Adarsh Sharma <adarsh(dot)sharma(at)orkash(dot)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(dot)sharma(at)orkash(dot)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
>>
>>
>
>
From | Date | Subject | |
---|---|---|---|
Next Message | raghu ram | 2011-05-03 10:54:34 | Can we Flush the Postgres Shared Memory ? |
Previous Message | Sam Stearns | 2011-05-03 06:53:43 | Unable to Insert Row |