Re: Tools available to determine bad code in the testing phase

From: Julien Rouhaud <rjuju123(at)gmail(dot)com>
To: Siraj G <tosiraj(dot)g(at)gmail(dot)com>
Cc: pgsql-admin(at)lists(dot)postgresql(dot)org
Subject: Re: Tools available to determine bad code in the testing phase
Date: 2023-10-19 04:25:58
Message-ID: pf7xaqsec3iwhipsy335bmdwguz4gkccows6qnsqosqbv35pf2@7ge6nua45eyl
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-admin

Hi,

On Wed, Oct 18, 2023 at 03:29:11PM -0400, Siraj G wrote:
> Hello All!
>
> I am new to PgSQL. I would like to know the tools available in PgSQL
> (similar to OEM, AWR/ASH, AppDynamics) using which we can determine the bad
> code performance wise and fix them timely during the development/soft
> go-live phases.

I think that the closest tool for postgres is PoWA, see
https://powa.readthedocs.io/en/latest/.

In response to

Browse pgsql-admin by date

  From Date Subject
Next Message Rajesh Kumar 2023-10-19 04:30:31 Re: Table health
Previous Message Ron 2023-10-19 00:00:31 Re: pg_dump -Z6 (the default) can be pretty slow