Re: clock_timestamp() and transaction_timestamp() function
От | Peter Eisentraut |
---|---|
Тема | Re: clock_timestamp() and transaction_timestamp() function |
Дата | |
Msg-id | Pine.LNX.4.44.0312011145140.22821-100000@peter.localdomain обсуждение исходный текст |
Ответ на | Re: clock_timestamp() and transaction_timestamp() function (Bruce Momjian <pgman@candle.pha.pa.us>) |
Ответы |
Re: clock_timestamp() and transaction_timestamp() function
Re: clock_timestamp() and transaction_timestamp() function |
Список | pgsql-patches |
Bruce Momjian writes: > The goal was to give a unified API to the various time measurements: > > [clock|statement|transaction]_timestamp It would be very useful if we had a parameter that controlled whether current_timestamp maps to statement_timestamp or to transaction_timestamp. There seems to be quite some disagreement over this issue, and this would help resolve it and also prevent users from unnecessarily using nonstandard functions in their application. The name "clock_timestamp" seems kind of unfortunate. Where else would a time stamp come from if not from the clock? Why is this functionality needed anyway? It seems that it could only serve to produce nondeterministic, unreproduceable results. -- Peter Eisentraut peter_e@gmx.net
В списке pgsql-patches по дате отправления: