Hi Amit,
>>* When enable_hashjoin was off, it did not happen.
Let me correct my information to make sure.
As you may already know, I found "set enable_hashjoin = off" doesn't help in some cases
including my client's case.
It makes sense since in my understanding postgres refers to wrong column information
when executing of join of each child table due to mistakenly shared SubPlan as you explained.
I'd be happy if there are any work around.
Not using partitioned table with inheritance but using declarative partition could become a work around?
Would you hit upon any other work arounds?
Regards,
Takeshi Ideriha
