Re: Timing of 'SELECT 1'

From: "Merlin Moncure" <merlin(dot)moncure(at)rcsonline(dot)com>
To: "Alex J(dot) Avriette" <alex(at)posixnap(dot)net>
Cc: "PostgreSQL-development" <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Timing of 'SELECT 1'
Date: 2004-03-12 18:30:32
Message-ID: 6EE64EF3AB31D5448D0007DD34EEB34101AD8A@Herge.rcsinc.local
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Marc G. Fournier 2004-03-12 18:30:45 Re: [HACKERS] The Name Game: postgresql.net vs.
Previous Message Andrew Dunstan 2004-03-12 18:27:40 Re: Log rotation