X-Original-To: pgsql-sql-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.2]) by svr1.postgresql.org (Postfix) with ESMTP id 20870D1BB89 for ; Fri, 23 Apr 2004 12:07:55 -0300 (ADT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (neptune.hub.org [200.46.204.2]) (amavisd-new, port 10024) with ESMTP id 50669-03 for ; Fri, 23 Apr 2004 12:07:51 -0300 (ADT) Received: from bugs.unl.edu.ar (bugs.unl.edu.ar [168.96.132.208]) by svr1.postgresql.org (Postfix) with ESMTP id D8D19D1BA93 for ; Fri, 23 Apr 2004 12:07:50 -0300 (ADT) Received: from localhost (localhost [127.0.0.1]) by bugs.unl.edu.ar (Postfix) with ESMTP id 2CA1A11E59; Fri, 23 Apr 2004 12:07:38 -0300 (ART) Received: from bugs.unl.edu.ar ([127.0.0.1]) by localhost (bugs [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 00718-06; Fri, 23 Apr 2004 12:07:37 -0300 (ART) Received: from localhost (localhost [127.0.0.1]) by bugs.unl.edu.ar (Postfix) with ESMTP id 8927711E3B; Fri, 23 Apr 2004 12:07:37 -0300 (ART) From: Martin Marques To: Tom Lane Subject: Re: CONTEXT on PL/pgSQL Date: Fri, 23 Apr 2004 12:07:35 -0300 User-Agent: KMail/1.5.4 Cc: pgsql-sql@postgresql.org References: <200404231018.51461.martin@bugs.unl.edu.ar> <23173.1082729913@sss.pgh.pa.us> In-Reply-To: <23173.1082729913@sss.pgh.pa.us> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Message-Id: <200404231207.35886.martin@bugs.unl.edu.ar> X-Virus-Scanned: by amavisd-new-20030616-p7 (Debian) at unl.edu.ar X-Virus-Scanned: by amavisd-new at postgresql.org X-Spam-Status: No, hits=0.0 tagged_above=0.0 required=5.0 tests= X-Spam-Level: X-Archive-Number: 200404/260 X-Sequence-Number: 17635 El Vie 23 Abr 2004 11:18, Tom Lane escribi=F3: > Martin Marques writes: > > I have a simple function made with PL/pgSQL and when I call it I get th= is > > in the logs: > > > > 2004-04-23 10:15:32 [30669] LOG: statement: SELECT nodoSuperior(22) AS > > sup 2004-04-23 10:15:32 [30669] LOG: statement: SELECT $1 > > CONTEXT: PL/pgSQL function "nodosuperior" line 7 at assignment > > log_statement currently logs everything the parser sees, which includes > SQL commands generated by plpgsql. > > Arguably these facilities should be separated, but until someone > makes a serious effort to provide plpgsql debugging features, > it's likely that nothing will be done about it. Right now this is > almost the only technique available for seeing what's going on inside > a plpgsql function, and crummy as it is, it's better than nothing... So the CONTEXT line just tells where the statement was made? --=20 12:06:01 up 45 days, 16:30, 2 users, load average: 0.50, 0.46, 0.45 ----------------------------------------------------------------- Mart=EDn Marqu=E9s | select 'mmarques' || '@' || 'unl.edu.ar' Centro de Telematica | DBA, Programador, Administrador Universidad Nacional del Litoral -----------------------------------------------------------------