Message-ID: <96bad2085dce2585fc747e20eba0aec4364cd371.camel@j-davis.com>
Subject: Re: Export log_line_prefix(); useful for emit_log_hook.
From: Jeff Davis <pgsql@j-davis.com>
To: Michael Paquier <michael@paquier.xyz>
Cc: pgsql-hackers@postgresql.org
Date: Tue, 28 Jun 2022 22:32:31 -0700
In-Reply-To: <YruoG3wYsI0Jq/kC@paquier.xyz>
References: <39c8197652f4d3050aedafae79fa5af31096505f.camel@j-davis.com>
	 <YruoG3wYsI0Jq/kC@paquier.xyz>
Content-Type: text/plain; charset="UTF-8"
Mime-Version: 1.0
Content-Transfer-Encoding: 7bit
Archived-At: 
 <https://www.postgresql.org/message-id/96bad2085dce2585fc747e20eba0aec4364cd371.camel%40j-davis.com>
Precedence: bulk

On Wed, 2022-06-29 at 10:17 +0900, Michael Paquier wrote:
> On Tue, Jun 28, 2022 at 11:52:56AM -0700, Jeff Davis wrote:
> > Patch attached. Some kinds of emit log hooks might find it useful
> > to
> > also compute the log_line_prefix.
> 
> Have you played with anything specific that would require that?  I
> am fine to expose this routine, being mostly curious about what kind
> of recent format implemented with the elog hook would use it.

Just a slightly different format that is directly digestible by another
system, while still preserving what the original messages in the file
would look like.

There are other ways to do it, but it's convenient. If we use, e.g.,
csv or json format, we lose the log_line_prefix and would need to
regenerate it from the individual fields.

Regards,
	Jeff Davis