Re: Add contrib module pg_stat_log: cumulative statistics about server log messages

From: Daniel Gustafsson <daniel(at)yesql(dot)se>
To: Fabrizio Mello <fabrizio(at)planetscale(dot)com>
Cc: PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>, "mail(at)joeconway(dot)com" <mail(at)joeconway(dot)com>, "nik(at)postgres(dot)ai" <nik(at)postgres(dot)ai>
Subject: Re: Add contrib module pg_stat_log: cumulative statistics about server log messages
Date: 2026-09-03 07:58:10
Message-ID: 5D8BEEDE-8028-46C8-BC37-8E9F85ED384C@yesql.se
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

> On 18 Aug 2026, at 13:23, Fabrizio Mello <fabrizio(at)planetscale(dot)com> wrote:

> * Is contrib the right home, or would people rather see this as a
> builtin stats kind with a core pg_stat_* view? Contrib felt right for
> a first step since it exercises the custom stats API and is entirely
> optional, but I'm happy to go either way.

IMHO, contrib is not the right home for anything new. Either we think it's
important for production and place it in core or it should live as an external
extension.

Your email didn't motivate why this extension should be in core instead of
maintained as an external extension?

--
Daniel Gustafsson

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Xuneng Zhou 2026-09-03 08:09:51 Re: WAIT FOR NO_THROW option could use some documentation
Previous Message Andrei Lepikhov 2026-09-03 07:48:31 Re: SUM(int2)/SUM(int4) do not detect overflow of the int8 accumulator