Re: Unable to Insert Row

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Noted.  Thanks, Ross.


On Fri, May 6, 2011 at 2:02 AM, Ross J. Reedstrom <reedstrm@xxxxxxxx> wrote:
> On Thu, May 05, 2011 at 08:23:16AM +0930, Sam Stearns wrote:
>> Dump/restore of table resolved this problem.
>
> Yeah, the 'repair' advice was probably bleed over from some other open
> source database that suffers from table corruption more regularly.
>
> Any sort of on disk corruption in a postgresql DB leads me to start
> looking at my hardware very carefully: seldom is it the software that is
> at fault, at least in this case.
>
> Ross
> --
> Ross Reedstrom, Ph.D.                                 reedstrm@xxxxxxxx
> Systems Engineer & Admin, Research Scientist        phone: 713-348-6166
> Connexions                  http://cnx.org            fax: 713-348-3665
> Rice University MS-375, Houston, TX 77005
> GPG Key fingerprint = F023 82C8 9B0E 2CC6 0D8E  F888 D3AE 810E 88F0 BEDE
>
>>
>> On Wed, May 4, 2011 at 8:22 AM, Sam Stearns <samtstearns@xxxxxxxxx> 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@xxxxxxxxx> wrote:
>> >> ---------- Forwarded message ----------
>> >> From: Sam Stearns <samtstearns@xxxxxxxxx>
>> >> Date: Tue, May 3, 2011 at 6:32 PM
>> >> Subject: Re:  Unable to Insert Row
>> >> To: Adarsh Sharma <adarsh.sharma@xxxxxxxxxx>
>> >>
>> >>
>> >> 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@xxxxxxxxxx> 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
>> >>>>
>> >>>>
>> >>>
>> >>>
>> >>
>> >
>>
>> --
>> Sent via pgsql-admin mailing list (pgsql-admin@xxxxxxxxxxxxxx)
>> To make changes to your subscription:
>> http://www.postgresql.org/mailpref/pgsql-admin
>>
>
> --
> Sent via pgsql-admin mailing list (pgsql-admin@xxxxxxxxxxxxxx)
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/pgsql-admin
>

-- 
Sent via pgsql-admin mailing list (pgsql-admin@xxxxxxxxxxxxxx)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-admin



[Index of Archives]     [KVM ARM]     [KVM ia64]     [KVM ppc]     [Virtualization Tools]     [Spice Development]     [Libvirt]     [Libvirt Users]     [Linux USB Devel]     [Linux Audio Users]     [Yosemite Questions]     [Linux Kernel]     [Linux SCSI]     [XFree86]

  Powered by Linux