Chris Spotts writes:
> What do you want specifically as far as details for the test case? I
> exported just the table that that was reading from. Installed a new
> clean virtual machine ubuntu (jaunty) and then installed 8.4.0.
> Imported the table and definition. Ran the same query and th
Tom Lane wrote:
"Chris Spotts" writes:
many groups are you expecting in that query? Does the plan for the
array_agg query show hash or group aggregation?
GroupAggregate
Huh, there's no reason it should take much memory then. Maybe you've
found a memory leak. Can you pu
> -Original Message-
> From: Tom Lane [mailto:[email protected]]
> Sent: Tuesday, July 21, 2009 12:16 PM
> To: Chris Spotts
> Cc: [email protected]
> Subject: Re: [GENERAL] array_agg crash?
>
> "Chris Spotts" writes:
> >> many groups
"Chris Spotts" writes:
>> many groups are you expecting in that query? Does the plan for the
>> array_agg query show hash or group aggregation?
> GroupAggregate
Huh, there's no reason it should take much memory then. Maybe you've
found a memory leak. Can you put together a self-contained test
> >> How big were the arrays you were trying to push around here?
>
> > 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.
>
> Hm, maybe the problem is not so much array size as too many arra
"Chris Spotts" writes:
>>> 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?
> Like I'd said originally, there were no arrays that ended up being more 4
> 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
"Chris Spotts" writes:
> That seems to have fixed it in the sense that it doesn't crash, but I 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
interrupt
> "Chris Spotts" writes:
> > LOG: 0: autovacuum launcher process (PID 10264) was terminated
> by
> > signal 9: Killed
>
> Looks like the OOM killer is loose on your system. Disable memory
> overcommit in the kernel and things will get better.
> http://www.postgresql.org/docs/8.4/static/kern
I had one simple query that kept crashing the connection. It crashes
after several minutes.
Tried restarting, it still error'd at the same place.
Tried recreating the table it was selecting from, it still error'd at
the same place.
I rewrote the query with an ARRAY subselect and it finished fl
"Chris Spotts" writes:
> LOG: 0: autovacuum launcher process (PID 10264) was terminated by
> signal 9: Killed
Looks like the OOM killer is loose on your system. Disable memory
overcommit in the kernel and things will get better.
http://www.postgresql.org/docs/8.4/static/kernel-resources.htm
I had one simple query that kept crashing the connection. It crashes after
several minutes.
Tried restarting, it still error'd at the same place.
Tried recreating the table it was selecting from, it still error'd at the
same place.
I rewrote the query with an ARRAY subselect and it finished fl
12 matches
Mail list logo
