Message-ID: <d08cf648d2c983f54d572989bccbad00c4bf3712.camel@dalibo.com>
Subject: Re: logfmt and application_context
From: =?ISO-8859-1?Q?=C9tienne?= BERSAC <etienne.bersac@dalibo.com>
To: Daniel Gustafsson <daniel@yesql.se>
Cc: pgsql-hackers@lists.postgresql.org
Date: Tue, 26 Sep 2023 09:56:27 +0200
In-Reply-To: <B526E775-3681-4951-AF5C-D13B2B304818@yesql.se>
References: <7e5a39c66e85d3794f04936bf723df8ae2a0992d.camel@dalibo.com>
	 <B526E775-3681-4951-AF5C-D13B2B304818@yesql.se>
Organization: DALIBO
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
User-Agent: Evolution 3.46.4-2 
MIME-Version: 1.0
Archived-At: <https://www.postgresql.org/message-id/d08cf648d2c983f54d572989bccbad00c4bf3712.camel%40dalibo.com>
Precedence: bulk

Hi Daniel,

Thanks for the feedback.

Le mardi 05 septembre 2023 =C3=A0 11:35 +0200, Daniel Gustafsson a =C3=A9cr=
it=C2=A0:
> > On 30 Aug 2023, at 14:36, =C3=89tienne BERSAC <etienne.bersac@dalibo.co=
m> wrote:
>=20
> > ..what do you think of having logfmt output along json and CSV ?
>=20
> Less ideal is
> that there is no official formal definition of what logfmt is [...]=C2=A0=
 If we add
> support for it, can we reasonably expect that what we emit is what consum=
ers of
> it assume it will look like?

I didn't know logfmt had variation. Do you have a case of
incompatibility ?

Anyway, I think that logfmt will be better handled inside Postgres
rather than in an extension due to limitation in syslogger
extendability. I could send a patch if more people are interested in
this.


What do you think about application_context as a way to render e.g. a
web request UUID to all backend log messages ?


Regards,
=C3=89tienne