Hi,
I did look at this because of the thread about "nbatch overflow" [1].
And the patches I just posted in that thread resolve the issue for me,
in the sense that the reproducer [2] no longer fails for me.
But I think that's actually mostly an accident - the balancing reduces
nbatch, exchanging i
Thank you for review!
On 14/08/2025 10:34 PM, Heikki Linnakangas wrote:
On 31/07/2025 18:13, Konstantin Knizhnik wrote:
On 27/07/2025 8:24 PM, Konstantin Knizhnik wrote:
I still trying to understand the reason of DSA overflow in hash join.
In addition to two suspicious places where number
On 31/07/2025 18:13, Konstantin Knizhnik wrote:
On 27/07/2025 8:24 PM, Konstantin Knizhnik wrote:
I still trying to understand the reason of DSA overflow in hash join.
In addition to two suspicious places where number of buckets is
doubled without chek for overflow (nodeHash.c:1668 and
On 27/07/2025 8:24 PM, Konstantin Knizhnik wrote:
I still trying to understand the reason of DSA overflow in hash join.
In addition to two suspicious places where number of buckets is
doubled without chek for overflow (nodeHash.c:1668 and nodeHash.c:3290),
there is one more place where
I still trying to understand the reason of DSA overflow in hash join.
In addition to two suspicious places where number of buckets is doubled
without chek for overflow (nodeHash.c:1668 and nodeHash.c:3290),
there is one more place where number of batches is multiplied by
Hi hackers!
There is weird error rarely reproduced with sqlancer: `ERROR: invalid
DSA memory alloc request size 1140850688`: **
*-*
*
FinalizeAggregate(cost=114075075706156
