Re: [INTERFACES] Back end memory consumption (was Front end memory consumption in SELECT)

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: dougt(at)mugc(dot)cc(dot)monash(dot)edu(dot)au
Cc: pgsql-interfaces(at)postgreSQL(dot)org
Subject: Re: [INTERFACES] Back end memory consumption (was Front end memory consumption in SELECT)
Date: 1999-12-03 00:41:29
Message-ID: 29675.944181689@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-interfaces

Douglas Thomson <dougt(at)mugc(dot)cc(dot)monash(dot)edu(dot)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

Responses

Browse pgsql-interfaces by date

  From Date Subject
Next Message Douglas Thomson 1999-12-03 02:12:48 Re: [INTERFACES] Back end memory consumption (was Front end memory consumption in SELECT)
Previous Message Douglas Thomson 1999-12-02 23:30:10 Re: [INTERFACES] Back end memory consumption (was Front end memory consumption in SELECT)