From: | Thom Brown <thom(at)linux(dot)com> |
---|---|
To: | Mladen Gogala <mladen(dot)gogala(at)vmsinfo(dot)com> |
Cc: | pgsql-novice(at)postgresql(dot)org |
Subject: | Re: Transactional issue that begs for explanation |
Date: | 2010-09-10 10:33:07 |
Message-ID: | AANLkTinam1efvi8=kD+mS+hVf6rwbsaYAY+NaQbqCH9B@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-novice |
On 10 September 2010 11:27, Mladen Gogala <mladen(dot)gogala(at)vmsinfo(dot)com> wrote:
> Thom Brown wrote:
>>
>> This is quite odd. I've done exactly the same thing on 8.4.4 Gentoo
>> x64 and it returns the expected result so I haven't been able to
>> recreate it. What does the table contain after that series of events?
>>
>>
>
> Oh, the content is correct, 4 records are modified, 5,10,15 and 20 have all
> value 'DIV5'. I've been bitten by triggers before so I am testing the
> trigger behavior. The good news is that "before update" trigger doesn't fire
> twice, as is the case with Oracle. BTW, is there any simpler method to
> simulate DBMS_OUTPUT, other than using plperlu the way I did?
Please reply to all so everyone else can see your response. :) (list
copied in again for this message)
But I personally don't know of the best way to produce the logging you're after.
--
Thom Brown
Twitter: @darkixion
IRC (freenode): dark_ixion
Registered Linux user: #516935
From | Date | Subject | |
---|---|---|---|
Next Message | Thomas Kellerer | 2010-09-10 14:55:35 | Re: PostgreSQL article online - PDF |
Previous Message | Thom Brown | 2010-09-10 09:47:53 | Re: Transactional issue that begs for explanation |