Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1VtCWX-0007UX-Ge for pgsql-performance@arkaria.postgresql.org; Wed, 18 Dec 2013 08:30:33 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.80) (envelope-from ) id 1VtCWX-00065m-0H for pgsql-performance@arkaria.postgresql.org; Wed, 18 Dec 2013 08:30:33 +0000 Received: from makus.postgresql.org ([2001:4800:7903:4::125]) by malur.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1VtCWW-00065g-4l for pgsql-performance@postgresql.org; Wed, 18 Dec 2013 08:30:32 +0000 Received: from 88-190-26-230.rev.poneytelecom.eu ([88.190.26.230] helo=sd-30687.dedibox.fr) by makus.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1VtCWT-0006UB-4y for pgsql-performance@postgresql.org; Wed, 18 Dec 2013 08:30:31 +0000 Received: from [192.168.1.25] (gut75-2-82-66-247-92.fbx.proxad.net [82.66.247.92]) by sd-30687.dedibox.fr (Postfix) with ESMTPSA id 15CCA644913; Wed, 18 Dec 2013 09:30:28 +0100 (CET) Message-ID: <1387355427.2240.4.camel@localhost> Subject: Re: Current query of the PL/pgsql procedure. From: Guillaume Lelarge To: Yuri Levinsky Cc: "depesz@depesz.com" , "pgsql-performance@postgresql.org" , Craig James Date: Wed, 18 Dec 2013 09:30:27 +0100 In-Reply-To: References: <20131216102619.GA27781@depesz.com> Content-Type: text/plain; charset="UTF-8" X-Mailer: Evolution 3.8.5 (3.8.5-2.fc19) Mime-Version: 1.0 Content-Transfer-Encoding: 7bit X-Pg-Spam-Score: 1.0 (+) List-Archive: List-Help: List-ID: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: X-Mailing-List: pgsql-performance Precedence: bulk Sender: pgsql-performance-owner@postgresql.org On Mon, 2013-12-16 at 11:42 +0000, Yuri Levinsky wrote: > Dear Depesz, > This is very problematic solution: I have to change whole!!! my code to put appropriate comment with query text before any query execution. In addition I would like to know current execution plan, that seems to be impossible. This is very hard limitation let's say. In case of production issue I'll just unable to do it: the issue already happening, I can't stop procedure and start code change. > James, > I saw your reply: I see the function is running, it's just not clear that exactly and how this function doing. > This blog post (http://blog.guillaume.lelarge.info/index.php/post/2012/03/31/Profiling-PL/pgsql-functions) can probably help you profiling your PL/pgsql functions without modifying them. I'm interested in any comments you can have on the log_functions hook function. Regards. -- Guillaume http://blog.guillaume.lelarge.info http://www.dalibo.com -- Sent via pgsql-performance mailing list (pgsql-performance@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-performance