| From: | Birgit Laggner <birgit(dot)laggner(at)vti(dot)bund(dot)de> |
|---|---|
| To: | Grzegorz Jaśkiewicz <gryzman(at)gmail(dot)com> |
| Cc: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: transaction control in pl/pgsql |
| Date: | 2010-04-01 10:56:03 |
| Message-ID: | 4BB47BC3.4000906@vti.bund.de |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Hi Grzegorz,
sorry, but that doesn't help me, perhaps you could get a little bit clearer:
@a) Does the use of SAVEPOINT avoid memory overflow? I could not find an
explanation about memory use in the documentation of SAVEPOINT.
@b) Do you mean I should not process my data or I should not use plpgsql
to do that? In what way I'm trying to outsmart the software???
Thanks,
Birgit.
On 01.04.2010 12:35, Grzegorz Jaśkiewicz wrote:
> a) you can't explicitly control transactions in plpgsql. If you need
> some sort of a form of it, use save points.
> b) you are trying to outsmart database software, and this is just a
> biiig mistake, and you should stop doing that completely.
>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Grzegorz Jaśkiewicz | 2010-04-01 11:05:04 | Re: transaction control in pl/pgsql |
| Previous Message | Nikhil G. Daddikar | 2010-04-01 10:55:15 | Re: "1-Click" installer problems |