| From: | Samuel Gendler <sgendler(at)ideasculptor(dot)com> |
|---|---|
| To: | Craig James <cjames(at)emolecules(dot)com> |
| Cc: | Jeff Janes <jeff(dot)janes(at)gmail(dot)com>, Merlin Moncure <mmoncure(at)gmail(dot)com>, pgsql-performance(at)postgresql(dot)org |
| Subject: | Re: Is drop/restore trigger transactional? |
| Date: | 2012-08-07 22:01:28 |
| Message-ID: | CAEV0TzAEX6bPC2OKtSgiYgkK1htry4YaRXDiig5tQjRqOp-Daw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
On Tue, Aug 7, 2012 at 2:39 PM, Craig James <cjames(at)emolecules(dot)com> wrote:
>
> Obviously this is a very expensive trigger, but one that we can drop
> in a very specific circumstance. But we NEVER want to drop it for
> everyone. It seems like a very reasonable use-case to me.
>
>
Sounds like you should try doing the work inside the trigger conditionally
and see if that improves performance enough, since you aren't likely to get
anything that better suits your needs without patching postgres.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Merlin Moncure | 2012-08-07 22:02:31 | Re: Is drop/restore trigger transactional? |
| Previous Message | Craig James | 2012-08-07 21:39:58 | Re: Is drop/restore trigger transactional? |