Re: transaction control in pl/pgsql
| От | Birgit Laggner |
|---|---|
| Тема | Re: transaction control in pl/pgsql |
| Дата | |
| Msg-id | 4BB47BC3.4000906@vti.bund.de обсуждение исходный текст |
| Ответ на | Re: transaction control in pl/pgsql (Grzegorz Jaśkiewicz <gryzman@gmail.com>) |
| Ответы |
Re: transaction control in pl/pgsql
|
| Список | 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. >
В списке pgsql-general по дате отправления: