X-Original-To: pgsql-sql-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [64.117.224.130]) by svr1.postgresql.org (Postfix) with ESMTP id 9796CD1B8BD for ; Fri, 22 Aug 2003 10:10:46 -0300 (ADT) Received: from svr1.postgresql.org ([64.117.224.193]) by localhost (neptune.hub.org [64.117.224.130]) (amavisd-new, port 10024) with ESMTP id 31661-08 for ; Fri, 22 Aug 2003 10:10:18 -0300 (ADT) Received: from frmug.org (frmug-gw.frmug.org [193.56.58.252]) by svr1.postgresql.org (Postfix) with ESMTP id E8AEFD1B9F8 for ; Fri, 22 Aug 2003 10:10:13 -0300 (ADT) Received: from frmug.org (localhost [127.0.0.1]) by frmug.org (8.12.9/8.11.3/frmug-2.7/nospam) with ESMTP id h7MD9xg2007562 (using TLSv1/SSLv3 with cipher DHE-RSA-AES256-SHA (256 bits) verified NO) for ; Fri, 22 Aug 2003 15:10:01 +0200 (CEST) (envelope-from pgsql-sql@phoe.frmug.org) Received: (from uucp@localhost) by frmug.org (8.12.9/8.12.9/Submit) with UUCP id h7MD9xHo007561 for pgsql-sql@postgresql.org; Fri, 22 Aug 2003 15:09:59 +0200 (CEST) Received: (from elrond@localhost) by memo.frmug.org (8.11.6/8.11.6) id h7MD4C392235 for pgsql-sql@postgresql.org; Fri, 22 Aug 2003 15:04:12 +0200 (CEST) (envelope-from pgsql-sql@phoe.frmug.org) X-Authentication-Warning: memo.frmug.org: elrond set sender to pgsql-sql@phoe.frmug.org using -f Date: Fri, 22 Aug 2003 15:04:12 +0200 From: Bertrand Petit To: pgsql-sql@postgresql.org Subject: Re: "SELECT IN" Still Broken in 7.4b Message-ID: <20030822150412.A92042@memo.frmug.org> Mail-Followup-To: pgsql-sql@postgresql.org References: <18608.1061411539@sss.pgh.pa.us> <20030822083232.C81672@memo.frmug.org> <5975.1061556615@sss.pgh.pa.us> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5.1i In-Reply-To: <5975.1061556615@sss.pgh.pa.us>; from tgl@sss.pgh.pa.us on Fri, Aug 22, 2003 at 08:50:15AM -0400 X-Virus-Scanned: by amavisd-new at postgresql.org X-Archive-Number: 200308/276 X-Sequence-Number: 14892 On Fri, Aug 22, 2003 at 08:50:15AM -0400, Tom Lane wrote: > Bertrand Petit 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