Re: How to prevent vacuum and reindex from deadlocking.
| От | Alvaro Herrera |
|---|---|
| Тема | Re: How to prevent vacuum and reindex from deadlocking. |
| Дата | |
| Msg-id | 20030813054507.GA3078@dcc.uchile.cl обсуждение |
| Ответ на | Re: How to prevent vacuum and reindex from deadlocking. (Robert Creager <Robert_Creager@LogicalChaos.org>) |
| Ответы |
Re: How to prevent vacuum and reindex from deadlocking.
|
| Список | pgsql-general |
On Tue, Aug 12, 2003 at 10:06:04PM -0600, Robert Creager wrote: > Thanks for point that out to me. I dare say that the BEGIN documentation is > unclear to me, even knowing what I know now. Why not just explictly say "Nested > transactions are not supported", rather than "... The current transaction is > not affected". Alright, maybe I still read at Junior High level. You have to keep in mind that inside PL/pgSQL, the "BEGIN" keyword has a different meaning, unrelated to the BEGIN keyword in SQL. In PL/pgSQL, BEGIN starts a code block, and has nothing to do at all with transactions. (I _think_ the original question had something to do with a PL/pgSQL function -- if this is not the case, please ignore.) -- Alvaro Herrera (<alvherre[a]dcc.uchile.cl>) "La espina, desde que nace, ya pincha" (Proverbio africano)
В списке pgsql-general по дате отправления: