Re: tracking commit timestamps
От | Peter Eisentraut |
---|---|
Тема | Re: tracking commit timestamps |
Дата | |
Msg-id | 5457F2F3.6070308@gmx.net обсуждение исходный текст |
Ответ на | Re: tracking commit timestamps (Petr Jelinek <petr@2ndquadrant.com>) |
Ответы |
Re: tracking commit timestamps
Re: tracking commit timestamps |
Список | pgsql-hackers |
On 11/1/14 8:04 AM, Petr Jelinek wrote: > On second thought, maybe those should be pg_get_transaction_committs, > pg_get_transaction_committs_data, etc. Please don't name anything "committs". That looks like a misspelling of something. There is nothing wrong with pg_get_transaction_commit_timestamp() If you want to reduce the length, lose the "get". > For me the commit time thing feels problematic in the way I perceive it > - I see commit time as a point in time, where I see commit timestamp (or > committs for short) as something that can recorded. So I would prefer to > stick with commit timestamp/committs. In PostgreSQL, it is pretty clearly established that time is hours, minutes, seconds, and timestamp is years, months, days, hours, minutes, seconds. So unless this feature only records the hour, minute, and second of a commit, it should be "timestamp".
В списке pgsql-hackers по дате отправления: