NunoACHenriques <nach@fct.unl.pt> writes:
> On Sun, 9 Jun 2002, Tom Lane wrote:
>> Is the data in the tables changing constantly?
> Not constantly, once a day.
Can't you set up a situation where the failure is reproducible, then?
On a day where you get the failure, dump the database and see if
you can load the data into a fresh database and reproduce the problem.
I spent some time looking at the tuplesort code and could not see any
reason for this failure. All that code has been fairly stable since
it was written for 7.0, and AFAIR no one else has reported this error
message. So either you've got a quite-unusual corner case that's
tickling a previously unseen bug, or you've got flaky hardware that for
some reason is manifesting in this way.
I don't necessarily believe the flaky-hardware theory, but I can't
make much progress on the bug theory without a test case to look at.
regards, tom lane
