Re: WIP: push AFTER-trigger execution into ModifyTable node

From: Marko Tiikkaja <marko(dot)tiikkaja(at)cs(dot)helsinki(dot)fi>
To: Robert Haas <robertmhaas(at)gmail(dot)com>
Cc: Greg Stark <gsstark(at)mit(dot)edu>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: WIP: push AFTER-trigger execution into ModifyTable node
Date: 2009-11-01 15:12:36
Message-ID: 4AEDA564.9000203@cs.helsinki.fi
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Robert Haas wrote:
> You'd also have to disallow the case when there are any triggers on
> the INSERT, or where there are any triggers on anything else (because
> they might access the target table of the INSERT). This will end up
> being so restricted as to be useless.

I might be wrong here, but I don't think it matters because those
trigger calls would have a different snapshot, right? Or am I missing
something?

Regards,
Marko Tiikkaja

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2009-11-01 15:12:41 Re: WIP: push AFTER-trigger execution into ModifyTable node
Previous Message Robert Haas 2009-11-01 15:02:18 Re: per-tablespace random_page_cost/seq_page_cost