From: | Scott Marlowe <scott(dot)marlowe(at)gmail(dot)com> |
---|---|
To: | Anj Adu <fotographs(at)gmail(dot)com>, pgsql-admin(at)postgresql(dot)org |
Subject: | Re: commit within function |
Date: | 2009-07-16 19:03:33 |
Message-ID: | dcc563d10907161203g51e2443ct3f0abf7ad9a9f977@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
On Thu, Jul 16, 2009 at 11:30 AM, Anj Adu<fotographs(at)gmail(dot)com> wrote:
> I need an explicit commit...i.e i need func B's results to be
> available to other transactions when I enter func C
>
> So...what you are saying is..in Func c
>
> BEGIN
> simulate error
> EXCEPTION
> WHEN condition [ OR condition ... ] THEN
> do nothing;
> END;
>
> Will this cause the transaction to be committed upto the savepoint in
> the beginning of function C ?
The transaction will be committed or not as a whole. That's how
transactions work. If you need part of the data so far processed
committed then you need to commit the transaction and start a new one.
From | Date | Subject | |
---|---|---|---|
Next Message | Scott Marlowe | 2009-07-16 19:14:55 | Re: PostgreSQL using 100% CPU |
Previous Message | Kevin Grittner | 2009-07-16 19:00:22 | Re: user connection properties |