From: Tom Lane <tgl@sss.pgh.pa.us>
To: dougt@mugc.cc.monash.edu.au
Cc: pgsql-interfaces@postgreSQL.org
Subject: Re: [INTERFACES] Back end memory consumption (was Front end memory consumption in SELECT)
Date: Thu, 02 Dec 1999 19:41:29 -0500
Message-ID: <29675.944181689@sss.pgh.pa.us> (raw)
In-Reply-To: <199912022330.KAA03178@mugca.cc.monash.edu.au>
Douglas Thomson <dougt@mugc.cc.monash.edu.au> writes:
> I have just noticed that the back end process swells to
> the total size of all the tables involved in my query for the
> duration of the SELECT (or is it the duration of the declared cursor
> now?).
The life of the cursor, probably, but I'm a little surprised by this.
> To summarise the situation:
> - I am attempting a join on 9 tables, using a cursor to fetch the
> selected data
> - the back end process grows to over 20M while processing my query
What query plan does EXPLAIN show for your SELECT?
regards, tom lane
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-interfaces@postgresql.org
Cc: tgl@sss.pgh.pa.us, dougt@mugc.cc.monash.edu.au
Subject: Re: [INTERFACES] Back end memory consumption (was Front end memory consumption in SELECT)
In-Reply-To: <29675.944181689@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox