Re: Large arrays give long lag on server side before command executes

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Steve Crawford <scrawford(at)pinpointresearch(dot)com>
Cc: David Helgason <david(at)uti(dot)is>, postgresql General <pgsql-general(at)postgresql(dot)org>
Subject: Re: Large arrays give long lag on server side before command executes
Date: 2004-09-24 23:42:51
Message-ID: 7016.1096069371@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Steve Crawford <scrawford(at)pinpointresearch(dot)com> writes:
> On Friday 24 September 2004 7:32 am, Tom Lane wrote:
>> I'm betting on some O(N^2) behavior in the array code, but it'll be
>> difficult to pinpoint without profile results.

> Possibly the bug we discussed early last year (IIRC added to todo but
> not fixed):
> http://archives.postgresql.org/pgsql-performance/2003-01/msg00235.php

No, it's not the same --- David sent me some results off-list and it
seems ReadArrayStr is the culprit. I'm not completely sure why yet.

FWIW, the printtup part of your gripe is fixed in CVS tip.

regards, tom lane

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Michael Fuhr 2004-09-25 01:50:35 cvs update: waiting for anoncvs's lock
Previous Message Steve Crawford 2004-09-24 23:12:40 Re: Large arrays give long lag on server side before command executes