Message-ID: <66181837-54c8-e3a5-e650-c789a4ffe29e@gmail.com>
Date: Fri, 8 Oct 2021 12:38:19 -0400
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:91.0) Gecko/20100101
 Thunderbird/91.1.0
Subject: Re: Better, consistent instrumentation for postgreSQL using a similar
 API as Oracle
Content-Language: en-US
To: Bruce Momjian <bruce@momjian.us>
Cc: pgsql-performance@lists.postgresql.org
References: 
 <CAMzkAgGAwh=vsUmtEOC-57GhbFo4eh_B7gJCWMqH4yR7hHJjgA@mail.gmail.com>
 <CAH2-Wzn-+=aYrMw4pHbV7yYVyRYskJkNLaV6HeHj94oyKJiRKA@mail.gmail.com>
 <efbd4d1a-48d5-99ac-549f-5e3f37812273@ardentperf.com>
 <4d9e6ac5-5b13-84fe-74b5-07421501318e@gmail.com>
 <20211008152132.GB31533@momjian.us>
From: Mladen Gogala <gogala.mladen@gmail.com>
In-Reply-To: <20211008152132.GB31533@momjian.us>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: 
 <https://www.postgresql.org/message-id/66181837-54c8-e3a5-e650-c789a4ffe29e%40gmail.com>
Precedence: bulk


On 10/8/21 11:21, Bruce Momjian wrote:
> Ah, this is exactly what I wanted to know --- what people are using the
> event waits for.  Can you tell if these are done all externally, or if
> they need internal database changes?
Well, the methodology goes like this: we get the slow queries from 
pgBadger report and then run explain (analyze, timing, buffers) on the 
query. If we still cannot figure out how to improve things, we check the 
events and see what the query is waiting for. After that we may add an 
index, partition the table, change index structure or do something like 
that. Unrelated to this discussion, I discovered Bloom extension. Bloom 
indexes are phenomenally useful. I apologize for the digression.

-- 
Mladen Gogala
Database Consultant
Tel: (347) 321-1217
https://dbwhisperer.wordpress.com