Re: Reducing memory usage of insert into select operations?

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: lists(at)stringsutils(dot)com
Cc: alvherre(at)commandprompt(dot)com, dev(at)archonet(dot)com, pgsql-general(at)postgresql(dot)org
Subject: Re: Reducing memory usage of insert into select operations?
Date: 2008-07-18 21:00:56
Message-ID: 10054.1216414856@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

"Francisco Reyes" <lists(at)stringsutils(dot)com> writes:
> What is the overhead for each AfterTriggerEvent?

On a 64-bit machine it looks like they'd cost you about 80 bytes
each :-(. A good deal of that is palloc overhead --- I wonder if
we should get rid of the separate-palloc-for-each-event design?

> When does the memory usage for those AfterTriggerEvents gets released? At
> commit?

Whenever the check is done; you'd have to read the rules about deferred
constraints ...

regards, tom lane

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Adrian Klaver 2008-07-18 21:04:04 Re: Calling Python functions with parameters
Previous Message Tom Lane 2008-07-18 20:55:12 Re: Reducing memory usage of insert into select operations?