Transactions ... - Mailing list pgsql-hackers

From The Hermit Hacker
Subject Transactions ...
Date
Msg-id Pine.BSF.4.21.9912141323310.34471-100000@thelab.hub.org
Whole thread Raw
Responses Re: [HACKERS] Transactions ...
List 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 by date:

Previous
From: Tom Lane
Date:
Subject: Re: [HACKERS] Re: [PATCHES] createdb/dropdb fixes
Next
From: The Hermit Hacker
Date:
Subject: [6.5.3] FATAL 1: my bits moved right off the end of the world!