Back before Christmas I complained that elog.c's behavior of
prioritizing LOG-level messages differently in standalone mode had
masked at least one significant bug, as well as causing confusion
in some other cases:
http://www.postgresql.org/message-id/6967.1355520...@sss.pgh.pa.us
I promptly
* Tom Lane (t...@sss.pgh.pa.us) wrote:
I promptly forgot to do anything about it, but I'd still like to get
such a change into 9.3. I've now written and tested a patch that
makes that change without creating any new noise during initdb or in a
manually-started standalone backend. Does anyone
On Fri, Dec 14, 2012 at 04:20:30PM -0500, Tom Lane wrote:
/* Determine whether message is enabled for server log output */
if (IsPostmasterEnvironment)
output_to_server = is_log_level_output(elevel, log_min_messages);
else
/* In bootstrap/standalone case, do not
In 3688.1355509...@sss.pgh.pa.us I complained
PS: one odd thing here is that the ereport(LOG) in
InstallXLogFileSegment isn't doing anything; otherwise we'd have gotten
a much more helpful error report about could not link file. I don't
think we run the bootstrap mode with log_min_messages
