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 523CAD1C516 for ; Mon, 17 May 2004 14:06:17 -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 74166-07 for ; Mon, 17 May 2004 14:05:54 -0300 (ADT) Received: from www.postgresql.com (www.postgresql.com [200.46.204.209]) by svr1.postgresql.org (Postfix) with ESMTP id 801B1D1CA64 for ; Mon, 17 May 2004 14:04:31 -0300 (ADT) Received: from mail.libertyrms.com (unknown [207.219.45.62]) by www.postgresql.com (Postfix) with ESMTP id 84F8ACF67FE for ; Mon, 17 May 2004 11:31:11 -0300 (ADT) Received: from dba4.int.libertyrms.com ([10.1.3.13] ident=ahammond) by mail.libertyrms.com with esmtp (Exim 4.22) id 1BPj98-0006sr-Om; Mon, 17 May 2004 10:31:14 -0400 Message-ID: <40A8CCEA.3000906@ca.afilias.info> Date: Mon, 17 May 2004 10:32:10 -0400 From: Andrew Hammond User-Agent: Mozilla Thunderbird 0.6 (X11/20040509) X-Accept-Language: en-us, en MIME-Version: 1.0 To: postgres SQL Cc: Eric Anderson Vianet SAO Subject: Re: view running query References: <20040512175750.12624.qmail@web41006.mail.yahoo.com> <069701c439d7$4cae4de0$0701a8c0@netterm> In-Reply-To: <069701c439d7$4cae4de0$0701a8c0@netterm> X-Enigmail-Version: 0.83.6.0 X-Enigmail-Supports: pgp-inline, pgp-mime Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 8bit X-SA-Exim-Mail-From: ahammond@ca.afilias.info X-SA-Exim-Scanned: No; SAEximRunCond expanded to false 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: 200405/148 X-Sequence-Number: 17862 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 There are two ways to do it. The server-side approach is to increase logging levels in the config file and then "pg_ctl reload". See http://www.postgresql.org/docs/7.4/interactive/runtime-config.html#RUNTIME-CONFIG-LOGGING for the stuff involved. The other way to do it is client side. In this case, you have to increase the logging level of your database connection. For example, if you have a perl DBD application, find the initilization of the database handle (by convention named $dbh) and then add $dbh->trace(2); After it. Drew Eric Anderson Vianet SAO wrote: | I run an application which connects to my pgsql DB. | | How could I see which query is sent to DB when, an example, i push some | application button (such ´find´). | | sds | | Eric Anderson | CPD Via Net SAO | 11-66432800 | | | ---------------------------(end of broadcast)--------------------------- | TIP 4: Don't 'kill -9' the postmaster -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQFAqMzogfzn5SevSpoRAnDwAJ4+y6xBwD9hXQ2k7V4mJbUf26rKLQCeP74Q HdgdLOV8bpqh5z4hgcUX52M= =dVN9 -----END PGP SIGNATURE-----