Horton

Re: delta relations in AFTER triggers

Adam Brusselback <adambrusselback@gmail.com>

View thread View on postgr.es
From: Adam Brusselback <adambrusselback@gmail.com>
To: Kevin Grittner <kgrittn@gmail.com>
Cc: Pg Hackers <pgsql-hackers@postgresql.org>
Date: 2016-11-02T21:09:04Z
Lists: pgsql-hackers 
>
> There may be some situations where crawling the indexes a row at a
> time will perform better than this by enough to want to retain that
> option.


If an index existed, wouldn't it still be able to use that in the set-based
implementation? Is there something which would make doing the check
set-based ever worse than row based inherently?

Commits

  1. Don't permit transition tables with TRUNCATE triggers.

  2. Pass EXEC_FLAG_REWIND when initializing a tuplestore scan.

  3. Faster expression evaluation and targetlist projection.

  4. Remove obsoleted code relating to targetlist SRF evaluation.

  5. Implement syntax for transition tables in AFTER triggers.