Re: Timing of 'SELECT 1' - Mailing list pgsql-hackers

From Merlin Moncure
Subject Re: Timing of 'SELECT 1'
Date
Msg-id 6EE64EF3AB31D5448D0007DD34EEB34101AD8A@Herge.rcsinc.local
Whole thread Raw
In response to Timing of 'SELECT 1'  (Bruce Momjian <pgman@candle.pha.pa.us>)
Responses Re: Timing of 'SELECT 1'  (Bruce Momjian <pgman@candle.pha.pa.us>)
List pgsql-hackers
> > The problem with gprof is that I am going to see all the backend
startup
> > stuff too, no?  Is there a way to get a dump just the run of the
query?
>
> I was sort of lurking on this thread, waiting to see what became of
it.
> Did
> nobody actually come to a conclusion on what that "last msec" was
from?

I think the consensus was it was coming from the network layer somehow.
If that's the case (it probably is), there isn't a whole lot that can be
done about it except to bypass it using server side functions and such.


Merlin


pgsql-hackers by date:

Previous
From: Andrew Dunstan
Date:
Subject: Re: Log rotation
Next
From: "Marc G. Fournier"
Date:
Subject: Re: [pgsql-www] The Name Game: postgresql.net vs.