| From: | Joel Jacobson <joel(at)trustly(dot)com> |
|---|---|
| To: | Andres Freund <andres(at)anarazel(dot)de> |
| Cc: | Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: autonomous transactions |
| Date: | 2016-09-02 07:21:50 |
| Message-ID: | CAASwCXcOKAzLp77WP10LV_0aiQuJxhd_BM2V_ey4FNY=iTQm4Q@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Thu, Sep 1, 2016 at 8:38 PM, Andres Freund <andres(at)anarazel(dot)de> wrote:
>
> I'm not convinced this makes much sense. All FDWs, dblink etc. already
> allow you do stuff outside of a transaction.
You as a DBA can prevent FDWs from being used and dblink is an
extension that you don't have to install.
So if preventing side-effects is necessary in your application, that
can be achieved by simply not installing dblink and preventing FDWs.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Rahila Syed | 2016-09-02 07:42:37 | Re: Surprising behaviour of \set AUTOCOMMIT ON |
| Previous Message | Vik Fearing | 2016-09-02 07:19:41 | Re: Sample configuration files |