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 | ff301166a9a6f23527277b89495ce56973a409f3 (patch) | |
| tree | ab94f938fe0985308c1e05f7fe3a7399a9461fe2 /src/backend/executor/nodeModifyTable.c | |
| parent | e7d3a37d9936f725807b4d5cdf471123a4805ef1 (diff) | |
| download | postgresql-ff301166a9a6f23527277b89495ce56973a409f3.tar.gz postgresql-ff301166a9a6f23527277b89495ce56973a409f3.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/backend/executor/nodeModifyTable.c')
0 files changed, 0 insertions, 0 deletions