pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Scott Marlowe <smarlowe@g2switchworks.com>
To: Adam Witney <awitney@sghms.ac.uk>
Cc: Tom Lane <tgl@sss.pgh.pa.us>
Cc: pgsql-admin <pgsql-admin@postgresql.org>
Subject: Re: Determine current running query,
Date: Tue, 29 Mar 2005 10:02:42 -0600
Message-ID: <1112112162.22988.32.camel@state.g2switchworks.com> (raw)
In-Reply-To: <BE6F37D3.4358F%awitney@sghms.ac.uk>
References: <BE6F37D3.4358F%awitney@sghms.ac.uk>

On Tue, 2005-03-29 at 09:50, Adam Witney wrote:
> On 29/3/05 4:27 pm, "Tom Lane" <tgl@sss.pgh.pa.us> wrote:
> 
> > Adam Witney <awitney@sghms.ac.uk> writes:
> >> Shouldn't there be something in current_query?
> > 
> > Only if (a) you have stats_command_string turned on, *and* (b) you
> > are a superuser or the owner of the target process.
> 
> I am logged in as the superuser, and I just switched stats_command_string
> on. Table now looks like this
> 
> bugasbase=# SELECT * from pg_stat_activity ;
>   datid   |  datname  | procpid | usesysid | usename | current_query |
> query_start        
> ----------+-----------+---------+----------+---------+---------------+------
> --------------------------
>  80573819 | bugasbase |   23197 |        1 | pgsql   | <IDLE>        |
> 29/03/2005 17:03:25.911288 BST
>  80573819 | bugasbase |   23195 |      109 | lubrook |               |
> 
> I did find a reference on google to the fact that there was/is a max query
> size length for this? I think this was for 7.3.5, is this still the case?
> Maybe this is the reason it is not showing up (it is quite a large query
> string)?

You might want to post your reference.  There hasn't been a built-in
query length limit for quite some time now.  MySQL's benchmark, by the
way, erroneously listed postgresql as having a 16 meg max query size
because (tada!) they had a 16 meg buffer allocated in their benchmark
and when it filled up and errored out the size was 16 meg.  I don't
believe this was ever fixed, either in their code or in the report they
had for a very long time on their web site.  And it was pointed out
again and again, by me.



view thread (3+ messages)  latest in thread

Message-ID: <1112112162.22988.32.camel@state.g2switchworks.com>
Permalink:  ../1112112162.22988.32.camel@state.g2switchworks.com/
Also on:    postgresql.org/message-id/1112112162.22988.32.camel@state.g2switchworks.com

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients from your mail client; the link fills in
  the headers below: reply via email
  Some clients, webmail especially, drop In-Reply-To and References from
  a link, and the reply then starts a new thread: use the mbox below.

  To: pgsql-admin@postgresql.org
  Cc: smarlowe@g2switchworks.com, awitney@sghms.ac.uk, tgl@sss.pgh.pa.us
  Subject: Re: Determine current running query,
  In-Reply-To: <1112112162.22988.32.camel@state.g2switchworks.com>
  References: <BE6F37D3.4358F%awitney@sghms.ac.uk> <1112112162.22988.32.camel@state.g2switchworks.com>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox