Re: Additional current timestamp values
От | Kevin Grittner |
---|---|
Тема | Re: Additional current timestamp values |
Дата | |
Msg-id | 442C1A4A.EE98.0025.0@wicourts.gov обсуждение исходный текст |
Ответ на | Re: Additional current timestamp values (Bruce Momjian <pgman@candle.pha.pa.us>) |
Ответы |
Re: Additional current timestamp values
Re: Additional current timestamp values |
Список | pgsql-patches |
>>> On Mon, Mar 20, 2006 at 7:58 pm, in message <200603210158.k2L1wMY01170@candle.pha.pa.us>, Bruce Momjian <pgman@candle.pha.pa.us> wrote: > Tom Lane wrote: >> But not once per statement --- in reality, you get a fairly arbitrary >> behavior that will advance in some cases and not others when dealing >> with a multi- statement querystring. >> "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". If it's not always in the form of a string, maybe "client xxx batch", where xxx could be statement, request, command, or query. -Kevin
В списке pgsql-patches по дате отправления: