"Fernando Hevia" <[EMAIL PROTECTED]> writes:
> The 'f_tasador' procedure is quite fast. As per log output I can see the
> procedure completes its execution within one second. Nevertheless in the LOG
> duration entry it shows a statement duration of over 36 secs.
It says milliseconds, not seconds.
> De: Richard Broersma [mailto:[EMAIL PROTECTED]
> Enviado el: Martes, 22 de Julio de 2008 17:19
>
> > 2008-07-22 15:52:37 ART|postgres| LOG: duration: 38.154 ms
>
> :o) You might be encountering a bit of parallax. This shows
> both 38 and 36 *milliseconds*.
>
That's embarrasing... I misto
On Tue, Jul 22, 2008 at 12:10 PM, Fernando Hevia <[EMAIL PROTECTED]> wrote:
>Nevertheless in the LOG
> duration entry it shows a statement duration of over 36 secs.
> ¿What is going on? ¿Where come those 36 seconds from?
> 2008-07-22 15:52:37 ART|postgres| LOG: duration: 38.154 ms
:o) You might
On Tue, 22 Jul 2008, Fernando Hevia wrote:
> I just enabled log duration in a 8.3.1 database and got puzzling
> information.
> I have a daemon shell-script run every 10 seconds the following:
>
>psql -c "select f_tasador();"
>
> The 'f_tasador' procedure is quite fast. As per log output I can
Hi list,
I just enabled log duration in a 8.3.1 database and got puzzling
information.
I have a daemon shell-script run every 10 seconds the following:
psql -c "select f_tasador();"
The 'f_tasador' procedure is quite fast. As per log output I can see the
procedure completes its execution w
