Peter Eisentraut wrote: > 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.
Agreed. You are thinking a GUC like statement_current_timestamp which defaults to false? -- Bruce Momjian | http://candle.pha.pa.us [EMAIL PROTECTED] | (610) 359-1001 + If your life is a hard drive, | 13 Roberts Road + Christ can be your backup. | Newtown Square, Pennsylvania 19073 ---------------------------(end of broadcast)--------------------------- TIP 8: explain analyze is your friend
