Hi,
Tom Lane wrote:
Hm, looks suspiciously ASCII-like. If you examine the page as text,
is it recognizable?
Doh! Yup, is recognizable. It looks like some PHP serialized output:
png%";i:84;s:24:"%InfoToolIconActive.png%";i:85;s:29:"%InfoToolIconHighlighted.png%";i:86;s:26:"%InfoToolIconInactive.png%";i:87;....
We do store serialized PHP objects like the above one in the database,
so it's probably not a mail spool.
What's the best cure? Can I just wipe out the block with something like:
# dd if=/dev/zero of=base/296788/302602 seek=58591 bs=8192 count=1
Yeah, try that. I think the net effect will be that some wide (toasted)
values will be truncated.
Thank you for you guidance. I've done that and hope the running pg_dump
goes through fine.
Regards
Markus
---------------------------(end of broadcast)---------------------------
TIP 9: In versions below 8.0, the planner will ignore your desire to
choose an index scan if your joining column's datatypes do not
match