Re: Changing behavior of BEGIN...sleep...do something...COMMIT

Поиск
Список
Период
Сортировка
От Doug McNaught
Тема Re: Changing behavior of BEGIN...sleep...do something...COMMIT
Дата
Msg-id m3k7ehvj0b.fsf@varsoon.wireboard.com
обсуждение исходный текст
Ответ на Re: Changing behavior of BEGIN...sleep...do something...COMMIT  (Bruce Momjian <pgman@candle.pha.pa.us>)
Ответы Re: Changing behavior of BEGIN...sleep...do something...COMMIT  (Bruce Momjian <pgman@candle.pha.pa.us>)
Список pgsql-hackers
Tom Lane <tgl@sss.pgh.pa.us> writes:

> Accordingly, it's a bad idea to invent now('clock') and make it the
> same function as the other flavors.  We could get away with making
> now('transaction') and now('statement') ---- but the argument for this
> was consistency, and that argument pretty much falls flat if those two
> are one function while clock time is something else.
> 
> So I'm back in the camp of thinking three separate parameterless
> functions are the way to do it.  We already know what now() does,
> and we're not going to change it --- anyone want to propose names
> for the other two?

Maybe clock_time() and statement_time(), with transaction_time() an
alias for now() (if that's seemed necessary)?

A little verbose perhaps, but clear...

-Doug



В списке pgsql-hackers по дате отправления:

Предыдущее
От: Tom Lane
Дата:
Сообщение: Re: Changing behavior of BEGIN...sleep...do something...COMMIT
Следующее
От: Bruce Momjian
Дата:
Сообщение: Re: Changing behavior of BEGIN...sleep...do something...COMMIT