Hi,
On Tue, Aug 26, 2025 at 06:38:41AM +, Bertrand Drouvot wrote:
> On Mon, Aug 25, 2025 at 08:28:04PM -0400, Andres Freund wrote:
> > FWIW, I think this was done wrongly for the per-backend IO stats too. I've
> > seen the increased overhead in profiles
>
> That's indeed something that could
Hi,
On Wed, Aug 27, 2025 at 01:57:13PM +, Bertrand Drouvot wrote:
> Hi,
>
> On Tue, Aug 26, 2025 at 04:55:09PM -0500, Sami Imseih wrote:
> > I worry that a single view will grow very wide, and we will have to
> > eventually
> > split it. So we may as well start thinking about having multiple
Hi,
On Tue, Aug 26, 2025 at 04:55:09PM -0500, Sami Imseih wrote:
> I worry that a single view will grow very wide, and we will have to eventually
> split it. So we may as well start thinking about having multiple views
> in advance.
I gave it more thoughts and I now think that multiple views is b
Hi,
On Tue, Aug 26, 2025 at 07:18:10AM -0400, Andres Freund wrote:
> Hi,
>
> On 2025-08-26 06:38:41 +, Bertrand Drouvot wrote:
> > > and IO related counters aren't
> > > incremented remotely as often as the scan related counters are.
> >
> > You mean the flush are not triggered as often? If
> > That is why I think we should be careful about naming. pg_stat_backend feels
> > very generic, but right now it only shows relation stats. Maybe we call it
> > pg_stat_backend_tables to start? Then if we later add I/O, we could have
> > pg_stat_backend_io, or for conflicts, pg_stat_backend_conf
Hi,
On 2025-08-26 06:38:41 +, Bertrand Drouvot wrote:
> > and IO related counters aren't
> > incremented remotely as often as the scan related counters are.
>
> You mean the flush are not triggered as often? If so, yeah that's also
> something
> you've mentioned ([1]) and that I've in mind t
Hi,
On Mon, Aug 25, 2025 at 05:51:38PM -0500, Sami Imseih wrote:
> Thanks for the patches.
>
> I have not gone through them in detail yet, but +1 on adding backend activity
> stats.
Thanks for sharing your thoughts.
> This provides another level of drill down to spot anomalous sessions or
> dif
Hi,
On Tue, Aug 26, 2025 at 06:38:41AM +, Bertrand Drouvot wrote:
> Hi,
>
> On Mon, Aug 25, 2025 at 08:28:04PM -0400, Andres Freund wrote:
> > I don't like that this basically doubles the overhead of keeping stats by
> > tracking everythign twice. The proper solution is to do that not in the
Hi,
On Mon, Aug 25, 2025 at 08:28:04PM -0400, Andres Freund wrote:
> Hi,
>
> On 2025-08-12 07:48:10 +, Bertrand Drouvot wrote:
> > From 9e2f8cb9a87f1d9be91f2f39ef25fbb254944968 Mon Sep 17 00:00:00 2001
> > From: Bertrand Drouvot
> > Date: Mon, 4 Aug 2025 08:14:02 +
> > Subject: [PATCH v1
Hi,
On Mon, Aug 25, 2025 at 07:22:43PM -0500, Sami Imseih wrote:
> > Adding these fields to the backend level stats spread based on the
> > backend PID without the knowledge of the relation they're related with
> > makes it much less interesting IMO, because we lose a lot of
> > granularity value
Hi,
On Tue, Aug 26, 2025 at 08:12:45AM +0900, Michael Paquier wrote:
> On Mon, Aug 25, 2025 at 05:51:38PM -0500, Sami Imseih wrote:
> > I have not gone through them in detail yet, but +1 on adding backend
> > activity
> > stats. This provides another level of drill down to spot anomalous sessions
Hi,
On 2025-08-12 07:48:10 +, Bertrand Drouvot wrote:
> From 9e2f8cb9a87f1d9be91f2f39ef25fbb254944968 Mon Sep 17 00:00:00 2001
> From: Bertrand Drouvot
> Date: Mon, 4 Aug 2025 08:14:02 +
> Subject: [PATCH v1 01/10] Adding per backend relation statistics tracking
>
> This commit introduce
> Adding these fields to the backend level stats spread based on the
> backend PID without the knowledge of the relation they're related with
> makes it much less interesting IMO, because we lose a lot of
> granularity value that we have with the pg_statio_* relations, at the
> cost of more bloat,
On Mon, Aug 25, 2025 at 05:51:38PM -0500, Sami Imseih wrote:
> I have not gone through them in detail yet, but +1 on adding backend activity
> stats. This provides another level of drill down to spot anomalous sessions or
> different patterns across applications. I also think we will want more than
Thanks for the patches.
I have not gone through them in detail yet, but +1 on adding backend activity
stats. This provides another level of drill down to spot anomalous sessions or
different patterns across applications. I also think we will want more than
just relation stats. For example, columns
15 matches
Mail list logo
