Frank van Vugt <[EMAIL PROTECTED]> writes:
> ERROR: invalid memory alloc request size 3248857576
> Obviously, since the backend keeps running, it won't be easy to get my hands
> on the backtrace from when this error occurs and I'm wondering about the best
> way to proceed in order to produce some helpfull input to the developers.
Provide a reproducible test case maybe?
Also, building with --enable-cassert might help track it down.
regards, tom lane
---------------------------(end of broadcast)---------------------------
TIP 9: the planner will ignore your desire to choose an index scan if your
joining column's datatypes do not match
