Transactions ...
От | The Hermit Hacker |
---|---|
Тема | Transactions ... |
Дата | |
Msg-id | Pine.BSF.4.21.9912141323310.34471-100000@thelab.hub.org обсуждение исходный текст |
Ответы |
Re: [HACKERS] Transactions ...
|
Список | pgsql-hackers |
Just a quick question. Am trying to debug some problems with UdmSearch, and the following being pumped out of hte backend (have debug mode's turned on) don't look right... StartTransactionCommand^M query: BEGIN WORK^M ProcessUtility: BEGIN WORK^M CommitTransactionCommand^M StartTransactionCommand^M query: INSERT INTO dict (url_id,word,intag) VALUES(810,'date',3)^M ProcessQuery^M CommitTransactionCommand^M StartTransactionCommand^M query: INSERT INTO dict (url_id,word,intag) VALUES(810,'support',3)^M ProcessQuery^M CommitTransactionCommand^M StartTransactionCommand^M query: INSERT INTO dict (url_id,word,intag) VALUES(810,'postgresql',1)^M ProcessQuery^M CommitTransactionCommand^M StartTransactionCommand^M query: INSERT INTO dict (url_id,word,intag) VALUES(810,'user',1)^M ProcessQuery^M CommitTransactionCommand^M StartTransactionCommand^M query: INSERT INTO dict (url_id,word,intag) VALUES(810,'s',1)^M ProcessQuery^M CommitTransactionCommand^M If they issue a 'BEGIN WORK', shouldn't it eliminate all the '{Commit,Start}TransactionCommand's? The man page shows: begin [transaction|work], but doesn't tell the difference between 'transaction' and 'work'... Comments? Thanks... Marc G. Fournier ICQ#7615664 IRC Nick: Scrappy Systems Administrator @ hub.org primary: scrappy@hub.org secondary: scrappy@{freebsd|postgresql}.org
В списке pgsql-hackers по дате отправления: