diff options
| author | Tom Lane <tgl@sss.pgh.pa.us> | 2018-03-18 15:10:28 -0400 |
|---|---|---|
| committer | Tom Lane <tgl@sss.pgh.pa.us> | 2018-03-18 15:10:28 -0400 |
| commit | 9fcc0baa7973eca67fae815cc5f1b62b493b3aef (patch) | |
| tree | 0f22c4d701c2ef1dc99c0aef8a2a83e3bf368cd6 /src/include/executor/nodeModifyTable.h | |
| parent | 24ff0fe87755c76a14332a03a08b62b85c9bc91d (diff) | |
| download | postgresql-9fcc0baa7973eca67fae815cc5f1b62b493b3aef.tar.gz postgresql-9fcc0baa7973eca67fae815cc5f1b62b493b3aef.zip | |
Doc: note that statement-level view triggers require an INSTEAD OF trigger.
If a view lacks an INSTEAD OF trigger, DML on it can only work by rewriting
the command into a command on the underlying base table(s). Then we will
fire triggers attached to those table(s), not those for the view. This
seems appropriate from a consistency standpoint, but nowhere was the
behavior explicitly documented, so let's do that.
There was some discussion of throwing an error or warning if a statement
trigger is created on a view without creating a row INSTEAD OF trigger.
But a simple implementation of that would result in dump/restore ordering
hazards. Given that it's been like this all along, and we hadn't heard
a complaint till now, a documentation improvement seems sufficient.
Per bug #15106 from Pu Qun. Back-patch to all supported branches.
Discussion: https://postgr.es/m/152083391168.1215.16892140713507052796@wrigleys.postgresql.org
Diffstat (limited to 'src/include/executor/nodeModifyTable.h')
0 files changed, 0 insertions, 0 deletions