Re: dblink() cursor error/issue (TopMemoryContext)

From: "Henry - Zen Search SA" <henry(at)zen(dot)co(dot)za>
To: "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: dblink() cursor error/issue (TopMemoryContext)
Date: 2008-06-13 16:27:47
Message-ID: 0111e2042ddcf6e90a90feced97d468f.squirrel@zenmail.co.za
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Fri, June 13, 2008 7:05 pm, Tom Lane wrote:
> How soon is "bang"?

I'll run it again and post back.

> The memory overhead per subtransaction is
> not zero, though I think it's fairly small if you don't have any
> triggers pending as a result of the insert.

Two triggers are fired for each insert (before and after trigs).

> (Hm ... any foreign keys on the table being inserted into?)

Not on the table being inserted into, but it has a couple of tables with
foreign keys referencing it.

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Tom Lane 2008-06-13 17:05:54 Re: dblink() cursor error/issue (TopMemoryContext)
Previous Message Henry - Zen Search SA 2008-06-13 14:46:15 Re: dblink() cursor error/issue (TopMemoryContext)