X-Original-To: pgsql-admin-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.144]) by svr1.postgresql.org (Postfix) with ESMTP id EB05652811 for ; Tue, 16 Aug 2005 01:36:36 -0300 (ADT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 48207-06 for ; Tue, 16 Aug 2005 04:36:34 +0000 (GMT) Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130]) by svr1.postgresql.org (Postfix) with ESMTP id 793AB52B06 for ; Tue, 16 Aug 2005 01:36:34 -0300 (ADT) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.13.1/8.13.1) with ESMTP id j7G4ZHC8023552; Tue, 16 Aug 2005 00:35:17 -0400 (EDT) To: adey Cc: Chris Hoover , pgsql-admin@postgresql.org Subject: Re: Any way to see what queries are currently running? In-reply-to: <1c66bda80508152107a29330e@mail.gmail.com> References: <1d219a6f05081513546f6458b6@mail.gmail.com> <1c66bda80508152107a29330e@mail.gmail.com> Comments: In-reply-to adey message dated "Tue, 16 Aug 2005 16:07:40 +1200" Date: Tue, 16 Aug 2005 00:35:17 -0400 Message-ID: <23551.1124166917@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0.006 required=5 tests=[AWL=0.006] X-Spam-Level: X-Archive-Number: 200508/189 X-Sequence-Number: 18508 adey writes: > You could try the following query after enabling the > stats_command_string parameter in the postgresql.conf file:- The pg_stat_activity mechanism *does* have a limit on the query string length it can display, and if memory serves that limit was not large in 7.3.* --- I'm thinking 256 bytes. However, the postmaster log doesn't have any hard limit that I'm aware of, so it seems like Chris' original approach should work. regards, tom lane