diff options
| author | Tom Lane <tgl@sss.pgh.pa.us> | 2001-03-14 21:47:50 +0000 |
|---|---|---|
| committer | Tom Lane <tgl@sss.pgh.pa.us> | 2001-03-14 21:47:50 +0000 |
| commit | c9f26d7af6537a332daf834c523d2de0c0390d65 (patch) | |
| tree | cf9c066fe831a86ace7f91c35dc493292bb13fb0 /src/backend/commands/trigger.c | |
| parent | 609fee47179aa4c8f7c93e7829658f114ceadd25 (diff) | |
| download | postgresql-c9f26d7af6537a332daf834c523d2de0c0390d65.tar.gz postgresql-c9f26d7af6537a332daf834c523d2de0c0390d65.zip | |
COPY should handle after-insert triggers the same as execMain.c does.
I'm not sure that it's really necessary to save insert events when there
are only after update or delete triggers, but certainly it's wrong for
COPY to behave differently from an INSERT query.
Diffstat (limited to 'src/backend/commands/trigger.c')
0 files changed, 0 insertions, 0 deletions