Re: tracking commit timestamps

Поиск
Список
Период
Сортировка
От Tom Lane
Тема Re: tracking commit timestamps
Дата
Msg-id 30058.1414764440@sss.pgh.pa.us
обсуждение исходный текст
Ответ на Re: tracking commit timestamps  (Merlin Moncure <mmoncure@gmail.com>)
Ответы Re: tracking commit timestamps
Список pgsql-hackers
Merlin Moncure <mmoncure@gmail.com> writes:
> It's also requested now and then in the context of auditing and
> forensic analysis of application problems.  But I also agree that the
> tolerance for performance overhead is got to be quite low.  If a GUC
> is introduced to manage the tradeoff, it should be defaulted to 'on'.

Alvaro's original submission specified that the feature defaults to "off".
Since there's no use-case for it unless you've installed some third-party
code (eg an external replication solution), I think that should stay true.
The feature's overhead might be small, but it is most certainly not zero,
and people shouldn't be paying for it unless they need it.
        regards, tom lane



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

Предыдущее
От: Tom Lane
Дата:
Сообщение: Re: Reducing Catalog Locking
Следующее
От: Robert Haas
Дата:
Сообщение: Re: group locking: incomplete patch, just for discussion