"Richard Huxton" <[EMAIL PROTECTED]> writes:
> Tom Lane <[EMAIL PROTECTED]> said:
> 2. Mark the timestamp() conversions as cachable
>>
>> This would be a BAD idea. Likely consequences include timestamp('now')
>> being evaluated at first use of a function, and not changing thereafter.
>> Probably
acao is null;
END IF;
Now execution time is <1s. Ok, but I really would like to know what's
happening to the older version.
Best Regards,
José Vilson de Mello de Farias
Dígitro Tecnologia Ltda. - Brazil
- Original Message -
From: Richard Huxton <[EMAIL PROTECTED]>
To: Vilson f
From: "Vilson farias" <[EMAIL PROTECTED]>
> Greetings,
>
> I found something very weird related with stored procedures execution.
I
> have this stored procedure to finalize a phone call, writing tha time of
> call finalization and some other values to a calls table, called
> cham_chamada. Ple
