Skip site navigation (1) Skip section navigation (2)

Re: Bug? Query plans / EXPLAIN using gigabytes of memory

From: Toby Corkindale <toby(dot)corkindale(at)strategicdata(dot)com(dot)au>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: Bug? Query plans / EXPLAIN using gigabytes of memory
Date: 2012-04-26 06:14:14
Message-ID: 4F98E7B6.506@strategicdata.com.au (view raw or flat)
Thread:
Lists: pgsql-general
On 26/04/12 15:30, Tom Lane wrote:
> Toby Corkindale<toby(dot)corkindale(at)strategicdata(dot)com(dot)au>  writes:
>> On 26/04/12 13:11, Tom Lane wrote:
>>> Well, if you were to provide a reproducible test case, somebody might be
>>> motivated to look into it.  There could be a memory leak in the planner
>>> somewhere, but without a test case it's not very practical to go look
>>> for it.
>
>> Would a Perl-based script that built up a database like that be a useful
>> test case for you?
>
> Yeah, sure, just something that somebody else can run to duplicate the
> problem.
>
>> For what it's worth, I discovered something quite interesting. The
>> memory usage only blows out when I do an update based on the results of
>> the query.
>
> Hm, is the update target an inheritance tree?

The target is the parent table of a bunch of partitions.
The actual rows being updated live in those child tables.

Toby

In response to

Responses

pgsql-general by date

Next:From: Tom LaneDate: 2012-04-26 06:58:06
Subject: Re: Bug? Query plans / EXPLAIN using gigabytes of memory
Previous:From: Tom LaneDate: 2012-04-26 05:30:14
Subject: Re: Bug? Query plans / EXPLAIN using gigabytes of memory

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group