| From: | Scott Marlowe <smarlowe(at)g2switchworks(dot)com> |
|---|---|
| To: | Alvaro Herrera <alvherre(at)surnet(dot)cl> |
| Cc: | Matt Miller <mattm(at)epx(dot)com>, PostgreSQL - GENERAL <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: Autonomous Transactions |
| Date: | 2005-06-01 16:11:41 |
| Message-ID: | 1117642301.20484.72.camel@state.g2switchworks.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Wed, 2005-06-01 at 10:52, Alvaro Herrera wrote:
> On Wed, Jun 01, 2005 at 03:38:01PM +0000, Matt Miller wrote:
> > I'm willing to use a different language, or even the libpq API if
> > necessary.
>
> If you really need autonomous transactions, you can establish an
> independent connection within a function in, say, PL/Perl or PL/Python.
> For example in PL/PerlU you can load the DBI driver and then use DBD::Pg
> to create another connection. Any command and transaction you initiate
> on that other connection will be, of course, completely separate and
> independent from the connection the function is executing in.
I've done the same thing here at work with dblink. Works a charm.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruno Wolff III | 2005-06-01 16:33:02 | Re: prevent user change password? |
| Previous Message | John DeSoi | 2005-06-01 16:06:18 | Re: Newby to DB |