| From: | Ian Lawrence Barwick <barwick(at)gmail(dot)com> |
|---|---|
| To: | Bruce Momjian <bruce(at)momjian(dot)us> |
| Cc: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: 9.3 release notes suggestions |
| Date: | 2013-05-04 11:34:18 |
| Message-ID: | CAB8KJ=jM-LXNbrKGBPMMedwn13NV_QZMrgR335vgBxSvxJXnsA@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
2013/4/24 Bruce Momjian <bruce(at)momjian(dot)us>:
> Thanks for the many suggestions on improving the 9.3 release notes.
> There were many ideas I would have never thought of. Please keep the
> suggestions coming.
One small suggestion:
<listitem>
<para>
Have <quote>session id</> (<literal>%c</>) in <link
linkend="guc-log-line-prefix"><varname>log_line_prefix</></link>
always output four hex digits after the period (Bruce Momjian)
</para>
</listitem>
This doesn't sound quite right - on OS X at least, PIDs go up to
99998, which means
%c may output 5 hex digits after the period. The following might be
more pedantically
accurate:
<listitem>
<para>
Have <quote>session id</> (<literal>%c</>) in <link
linkend="guc-log-line-prefix"><varname>log_line_prefix</></link>
always pad the PID value with zeros so at least four hex digits are
displayed after the period (Bruce Momjian)
</para>
</listitem>
if my slightly disengaged brain is grokking the source correctly:
src/backend/utils/error/elog.c:
appendStringInfo(buf, "%lx.%04x", (long) (MyStartTime), MyProcPid);
Regards
Ian Barwick
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Simon Riggs | 2013-05-04 12:49:39 | Re: In progress INSERT wrecks plans on table |
| Previous Message | Simon Riggs | 2013-05-04 10:16:20 | Re: corrupt pages detected by enabling checksums |