Tom Lane wrote:
> The underlined word is a field length word that evidently should contain
> 8, but contains hex 8008. This causes the tuple-data decoder to step
> way past the end of the tuple and off into never-never land. Since the
> results will depend on which shared buffer the page happens to be in and
> what happens to be at the address the step lands at, the inconsistent
> results from try to try are not so surprising.
Hmm, perhaps we could protect against "impossible" length words? (i.e.
those that would cause us try to read past the end of the current
buffer).
--
Alvaro Herrera http://www.CommandPrompt.com/
PostgreSQL Replication, Consulting, Custom Development, 24x7 support
