| From: | Petr Jelinek <petr(at)2ndquadrant(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Merlin Moncure <mmoncure(at)gmail(dot)com> |
| Cc: | Robert Haas <robertmhaas(at)gmail(dot)com>, Heikki Linnakangas <hlinnakangas(at)vmware(dot)com>, Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>, Pg Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: tracking commit timestamps |
| Date: | 2014-10-31 14:31:29 |
| Message-ID: | 54539D41.8020301@2ndquadrant.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | Postg토토 핫SQL : Postg토토 커뮤니티SQL : Postg토토 커뮤니티SQL 메일 링리스트 : 2014-10-31 이후 PGSQL WWW 14:31 |
On 31/10/14 15:07, Tom Lane wrote:
> Merlin Moncure <mmoncure(at)gmail(dot)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.
>
Agreed, that's why it stayed 'off' in my version too.
--
Petr Jelinek http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Simon Riggs | 2014-10-31 14:35:11 | Re: Column Redaction |
| Previous Message | Robert Haas | 2014-10-31 14:29:53 | Re: infinite loop in _bt_getstackbuf |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Petr Jelinek | 2014-10-31 15:46:35 | Re: tracking commit timestamps |
| Previous Message | Tom Lane | 2014-10-31 14:07:20 | Re: tracking commit timestamps |