]> granicus.if.org Git - postgresql/commit
projects / postgresql / commit
? search:
summary | shortlog | log | commit | commitdiff | tree
(parent: 609fee4) | patch
COPY should handle after-insert triggers the same as execMain.c does.
authorTom Lane <tgl@sss.pgh.pa.us>
Wed, 14 Mar 2001 21:47:50 +0000 (21:47 +0000)
committerTom Lane <tgl@sss.pgh.pa.us>
Wed, 14 Mar 2001 21:47:50 +0000 (21:47 +0000)
commitc9f26d7af6537a332daf834c523d2de0c0390d65
treecf9c066fe831a86ace7f91c35dc493292bb13fb0tree | snapshot
parent609fee47179aa4c8f7c93e7829658f114ceadd25commit | diff
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.
src/backend/commands/copy.c diff | blob | history
Unnamed repository; edit this file 'description' to name the repository.