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 B00D95294C for ; Tue, 16 Aug 2005 14:36:23 -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 52742-03 for ; Tue, 16 Aug 2005 17:36:22 +0000 (GMT) Received: from zproxy.gmail.com (zproxy.gmail.com [64.233.162.203]) by svr1.postgresql.org (Postfix) with ESMTP id F11F4528D4 for ; Tue, 16 Aug 2005 14:36:19 -0300 (ADT) Received: by zproxy.gmail.com with SMTP id 8so846527nzo for ; Tue, 16 Aug 2005 10:36:19 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=lntlGytzG3ene5/3wC+EH/2vlG1Ho8rqG1yZe0LdWFqC0PfRvEEI+AiQoRqi/bCxcbB4Gpm2HC67tKWQtw9NkYbTzw8nk44GAoh/MMYaIJ6OMeWvSb3j7P30Desex7BkQ5dylkDdm/noCy1X4d5i18tm9Nyd6omO+2cYPCOmKZA= Received: by 10.37.20.70 with SMTP id x70mr2055682nzi; Tue, 16 Aug 2005 10:36:19 -0700 (PDT) Received: by 10.36.24.2 with HTTP; Tue, 16 Aug 2005 10:36:19 -0700 (PDT) Message-ID: <1d219a6f05081610363089c0fe@mail.gmail.com> Date: Tue, 16 Aug 2005 13:36:19 -0400 From: Chris Hoover To: Tom Lane Subject: Re: Any way to see what queries are currently running? Cc: adey , pgsql-admin@postgresql.org In-Reply-To: <23551.1124166917@sss.pgh.pa.us> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline References: <1d219a6f05081513546f6458b6@mail.gmail.com> <1c66bda80508152107a29330e@mail.gmail.com> <23551.1124166917@sss.pgh.pa.us> X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0.024 required=5 tests=[RCVD_BY_IP=0.024] X-Spam-Level: X-Archive-Number: 200508/195 X-Sequence-Number: 18514 Ok, I was able to log the postgres.log and I found the entire query.=20 I am very sorry for causing this confusion. The way the query was being submitted made it look like it was being cut off, and our daily log files are multi-gig so mining them is quite a pain. (Also, I was quite under the weather yesterday). Anyway, it good to know there are some possible options besides always mining the logs. Thanks, Chris On 8/16/05, Tom Lane wrote: > adey writes: > > You could try the following query after enabling the > > stats_command_string parameter in the postgresql.conf file:- >=20 > 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. >=20 > However, the postmaster log doesn't have any hard limit that I'm > aware of, so it seems like Chris' original approach should work. >=20 > regards, tom lane >