Re: Waits monitoring

From: Rahul Pandey <rahul(dot)it(dot)cloud(dot)architect(at)gmail(dot)com>
To: Robert Haas <robertmhaas(at)gmail(dot)com>
Cc: Kyotaro HORIGUCHI <horiguchi(dot)kyotaro(at)lab(dot)ntt(dot)co(dot)jp>, Ildus Kurbangaliev <i(dot)kurbangaliev(at)postgrespro(dot)ru>, Amit Kapila <amit(dot)kapila16(at)gmail(dot)com>, Andres Freund <andres(at)anarazel(dot)de>, Simon Riggs <simon(at)2ndquadrant(dot)com>, Alexander Korotkov <a(dot)korotkov(at)postgrespro(dot)ru>, Masao Fujii <masao(dot)fujii(at)gmail(dot)com>, Haribabu Kommi <kommi(dot)haribabu(at)gmail(dot)com>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Waits monitoring
Date: 2024-12-03 16:24:54
Message-ID: CADcY+-yeJiPvt0+vK-u6dXYs0RuVmqzoJpqpv=_J3WMW9HAVFw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Is this supported on any of the public cloud managed postgres services?

On Tue, Dec 3, 2024 at 10:23 AM Robert Haas <robertmhaas(at)gmail(dot)com> wrote:

> On Thu, Sep 10, 2015 at 3:43 AM, Kyotaro HORIGUCHI
> <horiguchi(dot)kyotaro(at)lab(dot)ntt(dot)co(dot)jp> wrote:
> > Generated lwlocknames.[ch] don't have header comment because
> > generate-lwlocknames.pl writes them into wrong place.
> >
> > lmgr/Makefile looks to have some mistakes.
>
> Fixed.
>
> > - lwlocknames.c is not generated from (or using) lwlocknames.c
> > so the entry "lwlocknames.c: lwlocknames.h" doesn't looks to
> > be appropriate.
>
> I think that's a pretty standard way of handling a case where a single
> command generates multiple files.
>
> > - maintainer-clean in lmgr/Makefile forgets to remove lwlocknames.c.
>
> Fixed.
>
> > Perhaps uncommenting in pg_config_manual.h is left alone.
> > (This is not included in the diff below)
>
> Fixed.
>
> And committed. Thanks for the review, let's see what the buildfarm thinks.
>
> --
> Robert Haas
> EnterpriseDB: http://www.enterprisedb.com
> The Enterprise PostgreSQL Company
>
>
> --
> Sent via pgsql-hackers mailing list (pgsql-hackers(at)postgresql(dot)org)
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/pgsql-hackers
>
>
>

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Robert Haas 2024-12-03 16:39:43 checksum verification code breaks backups in v16-
Previous Message Peter Geoghegan 2024-12-03 16:21:04 Re: Why doesn't GiST VACUUM require a super-exclusive lock, like nbtree VACUUM?