From: | De Leeuw Guy <G(dot)De_Leeuw(at)eurofer(dot)be> |
---|---|
To: | Andrew Sullivan <ajs(at)crankycanuck(dot)ca> |
Cc: | pgsql-admin(at)postgresql(dot)org |
Subject: | Re: cache problem (v2) |
Date: | 2007-07-16 17:47:09 |
Message-ID: | 469BAF1D.8030108@eurofer.be |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
Hello Andrew,
Thanks for your attention
Andrew Sullivan a écrit :
> I tried to answer the previous version of this mail, but I don't
> understand it. Let me see if my questions trigger something for you,
> though.
>
> So if I am reading you correctly, IF code IN (1,2) THEN {do
> something}? What do you do then? I don't get this part.
>
I record a row with code = 3 and the value = the sum of each values in
code 1 & 2
> I don't see how this is possible either. You just deleted from test;
> how can you hae anything left in there?
>
I skip the delete action when the code is a sum code
>
>> maybe this is because these commands start a transaction with a cache
>> and each time that I request a select for a sum code that are on the
>> cache the value returned are not the real new value.
>>
>
> No, but a trigger that executes SQL can cause the trigger to fire
> again. Are you sure that's not happening?
>
>
Yes I test this situation on my trigger.
I sure about 99% that my problem come from the cache.
Regards
Guy
From | Date | Subject | |
---|---|---|---|
Next Message | Andrew Sullivan | 2007-07-16 18:48:37 | Re: cache problem (v2) |
Previous Message | Andrew Sullivan | 2007-07-16 17:09:57 | Re: cache problem (v2) |