Re: "SELECT IN" Still Broken in 7.4b

From: Bertrand Petit <pgsql-sql(at)phoe(dot)frmug(dot)org>
To: pgsql-sql(at)postgresql(dot)org
Subject: Re: "SELECT IN" Still Broken in 7.4b
Date: 2003-08-22 13:04:12
Message-ID: 20030822150412.A92042@memo.frmug.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-sql

On Fri, Aug 22, 2003 at 08:50:15AM -0400, Tom Lane wrote:
> Bertrand Petit <pgsql-sql(at)phoe(dot)frmug(dot)org> writes:
> > On Wed, Aug 20, 2003 at 04:32:19PM -0400, Tom Lane wrote:
> >> against actual elapsed time (cf psql's \timing option) would tell.
>
> > What is measured by the \timing option?
>
> Elapsed time ... as seen by the client, of course.

Is there a way to obtain the CPU time consumed by a query,
including a breakdown between user- and kernel-land?

--
%!PS
297.6 420.9 translate 90 rotate 0 setgray gsave 0 1 1{pop 0 180 moveto 100
180 170 100 170 -10 curveto 180 -9 180 -9 190 -10 curveto 190 100 100 180
0 180 curveto fill 180 rotate}for grestore/Bookman-LightItalic findfont
240 scalefont setfont -151.536392 -63.7998886 moveto (bp)show showpage

In response to

Browse pgsql-sql by date

  From Date Subject
Next Message Richard Huxton 2003-08-22 13:05:16 Re: Bug on parameter bigint in PL/PGSQL
Previous Message Stephan Szabo 2003-08-22 13:00:08 Re: Bug on parameter bigint in PL/PGSQL