From: | Christopher Kings-Lynne <chriskl(at)familyhealth(dot)com(dot)au> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | "Jonah H(dot) Harris" <jonah(dot)harris(at)gmail(dot)com>, Lane Van Ingen <lvaningen(at)esncc(dot)com>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: Need A Suggestion |
Date: | 2005-10-11 01:45:38 |
Message-ID: | 434B1942.1070604@familyhealth.com.au |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
> Whether this is a good idea is another question entirely. Lots of
> people will tell you it's a horrid idea for PG functions to cause
> outside-the-database side effects. The reason is that if the
> transaction that called the function aborts later, there is no way
> to roll back what was done outside the database, and so the state
> outside the database will no longer be in sync with the state inside.
The new solution for this is to use an XA transaction manager and 2PC I
guess...
Chris
From | Date | Subject | |
---|---|---|---|
Next Message | Christopher Kings-Lynne | 2005-10-11 01:47:32 | MySQL XA (Was Re: Need A Suggestion) |
Previous Message | Neil Conway | 2005-10-11 01:24:52 | Re: Need A Suggestion |