Re: transactions from PHP - double COMMIT required?
От | Martin Marques |
---|---|
Тема | Re: transactions from PHP - double COMMIT required? |
Дата | |
Msg-id | 45EC055B.80007@bugs.unl.edu.ar обсуждение исходный текст |
Ответ на | Re: transactions from PHP - double COMMIT required? (mikie <mikie.pl@gmail.com>) |
Ответы |
Re: transactions from PHP - double COMMIT required?
|
Список | pgsql-php |
mikie wrote: > 2007/3/2, Martin Marques <martin@bugs.unl.edu.ar>: >> mikie wrote: >> > 2007/3/1, Robert Treat <xzilla@users.sourceforge.net>: >> >> Yeah, do the above recommendation to see if all of your statements are >> >> making >> >> thier way into pg >> > >> > OK, I have checked the logs. I can see both COMMIT statements in the >> > log - the first commit from my transaction and then the other that I >> > send to workaround the problem. >> >> There must be some other problem. Do you have trasaction ID on the logs? >> See if both commits go in the same transaction. > > Could you please advise me how to check the transaction ID in the log? Edit postgresql.conf: log_line_prefix = '<%t %x>' And restart postmaster. >> Any errors during the transaction? > > As I wrote in my first post, I make this error intentionally to check > if transaction works (if something fails, then the entire transaction > should be rolled back). I intentionally give wrong data in the "date" > field for example. > Perhaps I should ask again: is it my responsibility to check if the > transaction failed and issue a ROLLBACK command, or will the PG server > do it automatically? One question: Why dont you but each query in a diferent pg_exec() command? -- 21:50:04 up 2 days, 9:07, 0 users, load average: 0.92, 0.37, 0.18 --------------------------------------------------------- Lic. Martín Marqués | SELECT 'mmarques' || Centro de Telemática | '@' || 'unl.edu.ar'; Universidad Nacional | DBA, Programador, del Litoral | Administrador ---------------------------------------------------------
В списке pgsql-php по дате отправления: