Message-ID: <3EA9F35A.848AB5D1@Yahoo.com>
Date: Fri, 25 Apr 2003 22:47:54 -0400
From: Jan Wieck <JanWieck@Yahoo.com>
Organization: Home
MIME-Version: 1.0
To: Bruce Momjian <pgman@candle.pha.pa.us>
Cc: Rajesh Kumar Mallah <mallah@trade-india.com>,
	pgsql-sql@postgresql.org
Subject: Re: /* */ comments showing up in pg_stat_activity
References: <200304251617.h3PGHWZ24565@candle.pha.pa.us>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

We do, but that wasn't the question.

I think you can asume that it'll stay that way because it is part of the
query string the backend is currently chewing on. What shows up in
pg_stat_activity is whatever was in the received query buffer before
starting to parse it. So we would have a hard time at that point to
filter out the comments.

The question back is from where does such a query with a comment come?
If it is a standard client like psql, it could happen someday that this
client does some filtering. If you're using libpq or another API that is
basically a libpq wrapper, you're pretty safe.


Jan

Bruce Momjian wrote:
> 
> Yes, we support /* */ comments.
> 
> ---------------------------------------------------------------------------
> 
> Rajesh Kumar Mallah wrote:
> >
> >
> >
> > Hmm ..
> > i just saw /* */ comments are being shown in current_query
> > is it ok ?
> >
> > More importantly is it supposed to remain like that ?
> > In that case i can tag every query with some identifier
> > to know from which application it originated when i check
> > em in pg_stat_activity !
> >
> >
> > regds
> > mallah.
>

-- 
#======================================================================#
# It's easier to get forgiveness for being wrong than for being right. #
# Let's break this rule - forgive me.                                  #
#================================================== JanWieck@Yahoo.com #