Re: elog tab indentation - Mailing list pgsql-hackers

From Bruce Momjian
Subject Re: elog tab indentation
Date
Msg-id 200310161711.h9GHBTX18294@candle.pha.pa.us
Whole thread Raw
In response to elog tab indentation  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: elog tab indentation  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
Tom Lane wrote:
> I observe that the server log is now indenting DETAIL/HINT lines:
> 
> LOG:  server process (PID 8468) was terminated by signal 6
> LOG:  terminating any other active server processes
> WARNING:  terminating connection because of crash of another server process
>     DETAIL:  The postmaster has commanded this server process to roll back the current transaction and exit, because
anotherserver process exited abnormally and possibly corrupted shared memory.
 
>     HINT:  In a moment you should be able to reconnect to the database and repeat your command.
> LOG:  all server processes terminated; reinitializing
> 
> This is not the behavior I thought we agreed to.

I thought DETAIL/HINT would be separate elog calls, and hence start at
the beginning of the line.  Are they all in on big elog string?  Sure
looks like it from the output.  Do we have to check the beginning of the
string for [A-Z]*:?

--  Bruce Momjian                        |  http://candle.pha.pa.us pgman@candle.pha.pa.us               |  (610)
359-1001+  If your life is a hard drive,     |  13 Roberts Road +  Christ can be your backup.        |  Newtown Square,
Pennsylvania19073
 


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: elog tab indentation
Next
From: Rod Taylor
Date:
Subject: Re: pg_autovacuum and VACUUM FREEZE