Re: Committed updates don't seem to be committed.
От | Frank Kurzawa |
---|---|
Тема | Re: Committed updates don't seem to be committed. |
Дата | |
Msg-id | D2F5697E-C4CD-11D8-8567-00039366F1F4@kurzawa.com обсуждение исходный текст |
Ответ на | Re: Committed updates don't seem to be committed. (Tom Lane <tgl@sss.pgh.pa.us>) |
Список | pgsql-novice |
Thanks Tom, I'm certainly open to the idea that there is a larger transaction wrapper that I am unaware of, but I will say this: When I saw that the commands were posted without error to the pgsql log, one of my first thoughts was that perhaps they were later rolled back. So I carefully reviewed everything in the log after the lines that I quoted and I can find nothing that even remotely resembles a statement or statements that would be related to a rollback. Nor were there any errors reported in the pgsql log. I'm not at work now, but will post more specifics from my code tomorrow. Moreover, my app is reasonably good at reporting any database-related errors that do occur, and I had none reported. I'm wondering if it is possibly some other database configuration issue. I confess to a fair amount of ignorance in this area. Regards, Frank On Jun 22, 2004, at 10:41 PM, Tom Lane wrote: > In particular, the quoted log segment only shows that this single > command executed successfully; it very possibly could have been part > of a larger transaction that later failed and was rolled back. > > I think Frank is in error to suppose that his updates are "not wrapped > in a transaction". > > regards, tom lane >
В списке pgsql-novice по дате отправления: