Re: elog tab indentation

From: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: pgsql-hackers(at)postgreSQL(dot)org
Subject: Re: elog tab indentation
Date: 2003-10-16 17:11:29
Message-ID: 200310161711.h9GHBTX18294@candle.pha.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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 another server 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(at)candle(dot)pha(dot)pa(dot)us | (610) 359-1001
+ If your life is a hard drive, | 13 Roberts Road
+ Christ can be your backup. | Newtown Square, Pennsylvania 19073

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Rod Taylor 2003-10-16 17:35:39 Re: pg_autovacuum and VACUUM FREEZE
Previous Message Tom Lane 2003-10-16 16:54:46 elog tab indentation