David Rowley <dgrowleyml(at)gmail(dot)com> writes:
> server closed the connection unexpectedly
Ugh.
> If I patch it with the attached rebustify_memoize_code.patch, I get:
> # explain analyze select * from t1 inner join t1 t2 on t1.a=t2.a where t1.a<=2;
> ERROR: unable to find memoization table entry
> My thoughts are that we likely should make this code more robust,
> despite the bug not being related to a broken data type. I'm only just
> over the fence on that one though. Any thoughts?
Strong +1, but please s/unable to/could not/, per message style
guidelines.
regards, tom lane