| From: | Peter Geoghegan <pg(at)heroku(dot)com> |
|---|---|
| To: | Stephen Frost <sfrost(at)snowman(dot)net> |
| Cc: | Robert Haas <robertmhaas(at)gmail(dot)com>, Dean Rasheed <dean(dot)a(dot)rasheed(at)gmail(dot)com>, Pg Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: INSERT ... ON CONFLICT UPDATE and RLS |
| Date: | 2015-01-07 23:14:03 |
| Message-ID: | CAM3SWZRzgH3u5QDHNGtwSJ8VAj-g4a2LSYyYdigMModEwLbigQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Wed, Jan 7, 2015 at 12:01 PM, Stephen Frost <sfrost(at)snowman(dot)net> wrote:
> Other databases have this capability and have triggers and at least one
> ends up firing both INSERT and UPDATE triggers, with many complaints
> from users about how that ends up making the performance suck. Perhaps
> we could use that as a fallback but support the explicit single trigger
> option too.. Just some thoughts, apologies if it's already been
> convered in depth previously.
I would like to expose whether or not statement-level triggers are
being called in the context of an INSERT ... ON CONFLICT UPDATE, FWIW.
--
Peter Geoghegan
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Geoghegan | 2015-01-07 23:34:08 | Re: INSERT ... ON CONFLICT UPDATE and RLS |
| Previous Message | Peter Eisentraut | 2015-01-07 22:31:56 | Re: Turning recovery.conf into GUCs |