Tom Lane writes:
Tatsuo Ishii <[EMAIL PROTECTED]> writes:
string_to_array() consumes too much memory. For example, to make
~70k array elements, string_to_array seems to eat several Gig bytes
of memory.

I'd argue that the problem comes from enlarging the work arrays only
64 elements at a time in accumArrayResult(). Most of the rest of the
code deals with resizing arrays using a "double it each time it has
to grow" approach, I wonder why this is different?

Without reading the code, I guess that simply means O(n^2) runtime. This should be fixed, then, right?

Best Regards,
Michael Paesold

---------------------------(end of broadcast)---------------------------
TIP 9: In versions below 8.0, the planner will ignore your desire to
      choose an index scan if your joining column's datatypes do not

Reply via email to