"Thompson, Shon" <Shon.Thompson@MaineGeneral.org> writes:
> I'm getting errors when I query a table that uses data type bytea. I can query the table if I don't include the
fieldfor data type bytea. Here are the two error messages I get. The first error is one generated from visual studio:
> "ERROR: XX000: invalid memory alloc request size 1294068297"
Looks like a corrupt-data problem. I doubt it's directly the fault of
bytea; any variable-length field would have given a similar type of error,
because what this seems to be is a damaged field length word.
Do you see any clearly bogus data in other columns of the table? That
might help isolate which row(s) have gotten damaged. It seems somewhat
unlikely that only the bytea field header would be clobbered and not
any adjacent data.
The questions you should be asking yourself include whether your PG
version is up-to-date and whether the storage stack is reliable.
regards, tom lane
