Re: Additional current timestamp values - Mailing list pgsql-patches

From Tom Lane
Subject Re: Additional current timestamp values
Date
Msg-id 2922.1143778042@sss.pgh.pa.us
Whole thread Raw
In response to Re: Additional current timestamp values  ("Kevin Grittner" <Kevin.Grittner@wicourts.gov>)
Responses Re: Additional current timestamp values
List pgsql-patches
"Kevin Grittner" <Kevin.Grittner@wicourts.gov> writes:
>>> "statement" isn't a great name for the units
>>> that we are actually processing.  We're really wanting to do these
>>> things once per client command, or maybe per client query would be
>>> a better name.
>>
>> Right.

> What about "query string"?  If you want to include the term "client", I
> would find "client query string" less confusing than "client command" or
> "client query".

"Query string" is a term we've used in the past, and it shows up in the
source code.  I could live with that, but I'm not sure if it's got any
good connotations for people who haven't got their hands dirty in the
code ...

            regards, tom lane

pgsql-patches by date:

Previous
From: "Kevin Grittner"
Date:
Subject: Re: Additional current timestamp values
Next
From: Jeremy Drake
Date:
Subject: patch to have configure check if CC is intel C compiler