Re: Please help with this error message

From: Dennis Gearon <gearond(at)cvc(dot)net>
To: Chris Smith <cdsmith(at)twu(dot)net>
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: Please help with this error message
Date: 2003-03-26 15:47:12
Message-ID: 3E81CB80.5080903@cvc.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

In general, I have seen no one complain about data integrity on this list unless
their hardware was bad. Search the arhives at:

http://marc.theaimsgroup.com/

under databases, postgres, for disk test and ram test software. Then test.

Chris Smith wrote:
> I posted about this earlier and got no response, but now it's happening
> again. Can someone please help?
>
> We're getting the following error message from PostgreSQL 7.3.2:
>
> ERROR: unexpected chunk number 1 (expected 0) for toast value 77579
>
> This error occurs whenever I attempt to SELECT the contents of a bytea field
> from this particular record. It has also occurred in the past, and appears
> to happen somewhat randomly among records. It does not appear to be related
> to the content of the data inserted into the database, because we've been
> able to retrieve the same actual contents successfully in other records.
>
> The INSERT and UPDATE to add the record and set the contents field work
> fine.
>
> Does anyone have any ideas on what I can try to solve this problem? I can
> put in a number of retries, I suppose, but that seems pretty kludgy.
>
> --
> www.designacourse.com
> The Easiest Way to Train Anyone... Anywhere.
>
> Chris Smith - Lead Software Developer/Technical Trainer
> MindIQ Corporation
>
>
> ---------------------------(end of broadcast)---------------------------
> TIP 1: subscribe and unsubscribe commands go to majordomo(at)postgresql(dot)org
>

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Manfred Koizar 2003-03-26 16:02:48 Re: postmaster has high CPU (system) utilization
Previous Message greg 2003-03-26 15:44:37 Re: How to prevent users from doing manually what my trigger should do for them?