Re: Non-empty default log_line_prefix
| От | Tom Lane |
|---|---|
| Тема | Re: Non-empty default log_line_prefix |
| Дата | |
| Msg-id | 32719.1476292303@sss.pgh.pa.us обсуждение |
| Ответ на | Re: Non-empty default log_line_prefix (Jeff Janes <jeff.janes@gmail.com>) |
| Ответы |
Re: Non-empty default log_line_prefix
Re: Non-empty default log_line_prefix |
| Список | pgsql-hackers |
Jeff Janes <jeff.janes@gmail.com> writes:
> On Sun, Oct 2, 2016 at 1:20 PM, Christoph Berg <myon@debian.org> wrote:
>> Patch attached. (Still using %t, I don't think %m makes sense for the
>> default.)
> What is the cost of using %m, other than 4 (rather compressible) bytes per
> log entry?
More log I/O, which is not free ... and that remark about compressibility
is bogus for anyone who doesn't pipe their postmaster stderr into gzip.
I'm already afraid that adding the timestamps will get us some pushback
about log volume.
regards, tom lane
В списке pgsql-hackers по дате отправления: