Re: [PATCHES] Implemented current_query - Mailing list pgsql-hackers

From Tom Lane
Subject Re: [PATCHES] Implemented current_query
Date
Msg-id 8823.1206807593@sss.pgh.pa.us
Whole thread Raw
In response to Re: [PATCHES] Implemented current_query  (Bruce Momjian <bruce@momjian.us>)
List pgsql-hackers
Bruce Momjian <bruce@momjian.us> writes:
> Uh, I think based on other usage it should be called client_statement().

That is *exactly* the wrong thing, because "statement" specifically
means one SQL statement.

"client_query" seems about the best compromise I've heard so far.

It's too bad we didn't have this debate before pg_stat_activity got out
into the wild, because it's now too late to rename its column
current_query.  Possibly we should stick with current_query() just
for consistency with that view ...
        regards, tom lane


pgsql-hackers by date:

Previous
From: Andrew Dunstan
Date:
Subject: Re: [DOCS] pg_total_relation_size() and CHECKPOINT
Next
From: Dean Rasheed
Date:
Subject: Re: [PATCHES] Auto-explain patch