| From: | "Chris Spotts" <rfusca(at)gmail(dot)com> |
|---|---|
| To: | "'Tom Lane'" <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: array_agg crash? |
| Date: | 2009-07-21 16:57:10 |
| Message-ID: | 00e401ca0a24$4b130ac0$e1392040$@com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
> killed
> > it after 15 minutes and no results...rather I tried to kill it, but
> it looks
> > like I'm going to have to -9 it...
>
> How big were the arrays you were trying to push around here? I tried
> interrupting a similar query and it came right back; but if you were
> building some really enormous arrays I could see the final array
> build loop taking awhile, and there's no CHECK_FOR_INTERRUPTS in it...
>
> regards, tom lane
[Spotts, Christopher]
Like I'd said originally, there were no arrays that ended up being more 4
elements long - all integers. The vast majority of them were 1 or 2 long.
If it was having trouble allocating the memory for arrays, why doesn't using
a ARRAY(subselect) yield the same issue?
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2009-07-21 17:02:57 | Re: array_agg crash? |
| Previous Message | Tom Lane | 2009-07-21 16:09:57 | Re: suggestion: log_statement = sample |