Inženjer — na latinskom znači inspirisan.
Inženjer može sve. (c) R.Dizel.
Epigrafi.

Ili priča o tome zašto administrator baza podataka treba da se seti svoje programerske prošlosti.
Predgovor
Sva imena su promenjena. Slučajna poklapanja. Materijal predstavlja isključivo lično mišljenje autora.
Odricanje od garancija: u planiranom ciklusu članaka neće biti detaljnog i tačnog opisa korišćenih tabela i skripti. Materijal se ne može odmah koristiti 'KAKO JESTE'.
Prvo, zbog velike količine materijala,
drugo, zbog specifičnosti proizvodne baze stvarnog naručioca.
Zato će članci sadržati samo ideje i opise u najopštijem smislu.
Možda će sistem u budućnosti napredovati do nivoa objavljivanja na GitHub-u, a možda i ne. Vreme će pokazati.
Početak priče - '».
Šta je na kraju ispalo, u najopštijim crtama - '»
Zašto mi je sve ovo potrebno?
Prvo, da ne zaboravim, sećajući se svojih dobrih dana u penziji.
Drugo, da sistematizujem napisanog. Jer već sam počeo da se gubim i zaboravljam pojedine delove.
I najvažnije — možda će nekome koristiti i pomoći da ne izmišlja bicikl i ne sakuplja grablje. Drugim rečima, da poboljša svoju karmu (ne Habr-ovu). Jer, najvrednije u ovom svetu su ideje. Ključno je pronaći ideju. A realizovati ideju u stvarnost je već isključivo tehničko pitanje.
Dakle, hajde da počnemo, polako...
Postavljanje zadatka.
Imamo:
Baza podataka PostgreSQL (10.5), mešovitog tipa opterećenja (OLTP+DSS), srednje-male opterećenosti, smeštena u oblaku AWS.
Monitoring baze podataka nije prisutan, monitoring infrastrukture je predstavljen u vidu standardnih sredstava AWS u minimalnoj konfiguraciji.
Potrebno je:
Pratiti performanse i stanje baze podataka, nalaziti i imati osnovne informacije za optimizaciju teških upita ka BDP.
Kratak uvod ili analiza opcija rešenja
Za početak pokušajmo razmotriti opcije rešenja zadatka sa stanovišta komparativne analize koristi i neprijatnosti za inženjera, dok se koristi i gubici menadžmenta prepuštaju onima kojima to pripada po radnoj biografiji.
Opcija 1 - 'Rad na zahtev'
Ostavimo sve kako jeste. Ako naručitelj nije zadovoljan nečim u funkcionalnosti, performansama baze podataka ili aplikacije, obavestit će DBA inženjere putem e-maila ili kreirati incident u sistemu za praćenje.
Inženjer, primivši obaveštenje, razmotriće problem, predložiti rešenje ili odložiti problem u dalju budućnost, nadajući se da će se sve samo rešiti, jer će ionako brzo zaboraviti.
Medenjaci i krofne, modrice i kvrgeMedenjaci i krofne:
1. Ne treba raditi ništa suvišno
2. Uvek postoji mogućnost izbegavanja obaveza.
3. Puno vremena koje se može potrošiti po vlastitom nahođenju.
Modrice i kvrge:
1. Pre ili kasnije, naručitelj će se zapitati o suštini postojanja i univerzalnoj pravdi u ovom svetu i još jednom postaviti pitanje — zašto plaćam svoje novce? Posledstvo je uvek isto — pitanje je samo kada će se naručitelj zasititi i odustati. A hranilište će se isprazniti. To je žalosno.
2. Razvoj inženjera — nula.
3. Teškoće u planiranju rada i opterećenja
Opcija 2 - „Ples sa bubnjevima, prodajemo i obuvamo“
Tačka 1-Zašto nam je potreban sistem monitoringa, dobijat ćemo sve putem zahteva. Pustamo gomilu raznih upita ka rečniku podataka i dinamičkim prikazima, uključujemo razne brojače, sve svodimo u tabele, povremeno kao da analiziramo liste i tabele. Kao rezultat imamo lepe ili ne baš lepe grafike, tabele, izveštaje. Glavno je — da bude što više, što više.
Tačka 2-Generišemo aktivnost — pokrećemo analizu svega ovoga.
Tačka 3-Pripremamo neki dokument, nazivamo ga jednostavno — „kako da uredimo bazu podataka“.
Tačka 4-Naručilac, videći svu tu veličanstvenost grafika i brojeva, preuzima detinjastu naivnost — sada će sve raditi, uskoro. I lako i bezbolno se odriče svojih finansijskih sredstava. Menadžment takođe veruje — naši inženjeri rade odlično. Opterećenje je na maksimumu.
Tačka 5-Redovno ponavljati Tačku 1.
Medenjaci i krofne, modrice i kvrgeMedenjaci i krofne:
1. Život menadžera i inženjera — jednostavan, predvidiv i ispunjen aktivnostima. Sve zuji, svi su zaposleni.
2. Život naručitelja takođe nije loš — uvek je siguran da treba još malo strpljenja i sve će se srediti. Ne sređuje se, pa, šta da se radi — svet je nepravedan, u sledećem životu — možda će imati sreće.
Modrice i kvrge:
1. Pr sooner or later, a faster provider of a similar service will emerge, doing the same thing but slightly cheaper. If the result is the same, why pay more? Again, this will lead to the disappearance of the feeding source.
2. It's boring. Just as boring as any meaningless activity.
3. Like the previous option, there's no development here. But for an engineer, the downside is that, unlike the first option, IBD needs to be constantly generated here. And that takes time. Time that could be spent on something more beneficial for yourself. Because if you don't take care of yourself, no one else will.
Option 3 - There's no need to reinvent the wheel; just buy one and ride.
Engineers from other companies don’t eat pizza washed down with beer for nothing (ah, the glorious times of St. Petersburg in the 90s). Let’s use monitoring systems that are built, debugged, and functional, which, generally speaking, bring value (at least to their creators).
Medenjaci i krofne, modrice i kvrgeMedenjaci i krofne:
1. You don't need to waste time on inventing what has already been invented. Just take it and use it.
2. Monitoring systems are created not by fools, and they are certainly useful.
3. Working monitoring systems usually provide useful filtered information.
Modrice i kvrge:
1. In this case, the engineer is not an engineer but merely a user of someone else's product. Or a user.
2. You have to convince the client of the necessity to buy something that, frankly speaking, they don’t want to deal with, and should not, and the annual budget has been approved and will not change. Then it requires allocating a separate resource to configure under a specific system. So, first, you have to pay, pay again, and pay once more. And the client is stingy. That's the norm of life.
What to do - Chernyshevsky? Your question is quite relevant. (c)
In this particular case and the existing situation, we can act a bit differently — let's create our own monitoring system.

Well, not a system in the full sense of the word, that's too grand and presumptuous, but at least make it easier for ourselves and gather more information for resolving performance incidents. So we won’t find ourselves in a situation of 'go there, I don’t know where, find that, I don’t know what.'
What are the pros and cons of this option:
Prednosti:
1. It's interesting. At least it's more interesting than constant 'shrink datafile, alter tablespace, etc.'
2. Ovo su nove vještine i nova razvijanja. Što će na duge staze konačno donijeti zaslužene nagrade i slastice.
Mane:
1. Morat ćete raditi. Raditi puno.
2. Morat ćete redovno objašnjavati smisao i perspektive svih aktivnosti.
3. Nešto ćete morati žrtvovati, jer je jedini resurs dostupan inženjeru – vrijeme – ograničeno svemirskim pravilima.
4. Najstrašnija i najneugodnija stvar — u rezultatima bi se moglo pojaviti nešto što nije ni miš, ni žaba, već neka nepoznata životinja.
Ko ne rizikuje, ne pije šampanjac.
Dakle, sada počinje najzanimljivije.
Opća ideja – u shematskoj formi

(Ilustracija je preuzeta iz članka «»)
Objašnjenje:
- U ciljnoj bazi se postavlja standardno proširenje PostgreSQL – “pg_stat_statements”.
- U bazi podataka za monitoring kreiramo skup servisnih tabela za pohranu historije pg_stat_statements u početnoj fazi i za podešavanje metrika i monitoringa u budućnosti
- Na hostu za monitoring kreiramo skup bash skripti, uključujući one za generisanje incidenata u sistemu tiketa.
Servisne tabele
Za početak, shematski pojednostavljena ERD, šta je na kraju rezultat:

Kratak opis tabelaendpoint — host, tačka povezivanja s instancom
database — parametri baze podataka
pg_stat_history — istorijska tabela za pohranu vremenskih snimaka prikaza pg_stat_statements ciljane baze podataka
metric_glossary — rečnik metrika performansi
metric_config — konfiguracija pojedinačnih metrika
metric — konkretna metrika za praćeni upit
metric_alert_history — istorija upozorenja iz performansi
log_query — pomoćna tabela za pohranu razrađenih zapisa iz loga PostgreSQL preuzetih sa AWS-a
baseline — parametri vremenskog perioda korišćeni kao osnovni
checkpoint — konfiguracija metrika za provjeru stanja baze podataka
checkpoint_alert_history — istorija upozorenja metrika provjere stanja baze podataka
pg_stat_db_queries — pomoćna tabela aktivnih upita
activity_log — pomoćna tabela dnevnika aktivnosti
trap_oid — pomoćna tabela konfiguracije zamke
Faza 1 — prikupljanje statističkih informacija o performansama i dobijanje izveštaja
Za pohranu statističkih informacija služi tabela pg_stat_history
Struktura tabele pg_stat_history
Tabela "public.pg_stat_history"
Kolona | Tip | Modifikatori
---------------------+-----------------------------+-------------------------------------------
id | celi broj | ne null podrazumijeva nextval('pg_stat_history_id_seq'::regclass)
snapshot_timestamp | vremenska oznaka bez vremenske zone |
database_id | celi broj |
dbid | oid |
userid | oid |
queryid | veliki broj |
query | tekst |
calls | veliki broj |
total_time | dvostruka preciznost |
min_time | dvostruka preciznost |
max_time | dvostruka preciznost |
mean_time | dvostruka preciznost |
stddev_time | dvostruka preciznost |
rows | veliki broj |
shared_blks_hit | veliki broj |
shared_blks_read | veliki broj |
shared_blks_dirtied | veliki broj |
shared_blks_written | veliki broj |
local_blks_hit | veliki broj |
local_blks_read | veliki broj |
local_blks_dirtied | veliki broj |
local_blks_written | veliki broj |
temp_blks_read | veliki broj |
temp_blks_written | veliki broj |
blk_read_time | dvostruka preciznost |
blk_write_time | dvostruka preciznost |
baseline_id | celi broj |
Indeksi:
"pg_stat_history_pkey" PRIMARNI KLJUČ, btree (id)
"database_idx" btree (database_id)
"queryid_idx" btree (queryid)
"snapshot_timestamp_idx" btree (snapshot_timestamp)
Strani ključevi:
"database_id_fk" STRANI KLJUČ (database_id) REFERENCIRA database(id) KADA SE IZLIJEKao što vidimo, tabela predstavlja samo kumulativne podatke prikaza pg_stat_statements u ciljnoj bazi podataka.
Korištenje ove tabele je vrlo jednostavno
pg_stat_history predstavljaće nagomilanu statistiku izvršavanja upita za svaku sedmicu. Na početku svake sedmice, nakon što se tabela popuni, statistika pg_stat_statements se resetuje pomoću pg_stat_statements_reset().
Napomena: statistika se prikuplja za upite čije vrijeme izvršenja traje više od 1 sekunde.
Popunjavanje tabele pg_stat_history
--pg_stat_history.sql
CREATE OR REPLACE FUNCTION pg_stat_history( ) RETURNS boolean AS $$
DECLARE
endpoint_rec record ;
database_rec record ;
pg_stat_snapshot record ;
current_snapshot_timestamp timestamp without time zone;
BEGIN
current_snapshot_timestamp = date_trunc('minute',now());
FOR endpoint_rec IN SELECT * FROM endpoint
LOOP
FOR database_rec IN SELECT * FROM database WHERE endpoint_id = endpoint_rec.id
LOOP
RAISE NOTICE 'NOVI SNIMAK SE STVARA';
--Povezivanje na ciljnu bazu podataka
EXECUTE 'SELECT dblink_connect(''LINK1'',''host='||endpoint_rec.host||' dbname='||database_rec.name||' user=USER password=PASSWORD '')';
RAISE NOTICE 'host % i dbname % ',endpoint_rec.host,database_rec.name;
RAISE NOTICE 'Stvaranje snimka pg_stat_statements za bazu podataka %',database_rec.name;
SELECT
*
INTO
pg_stat_snapshot
FROM dblink('LINK1',
'SELECT
dbid , SUM(calls),SUM(total_time),SUM(rows) ,SUM(shared_blks_hit) ,SUM(shared_blks_read) ,SUM(shared_blks_dirtied) ,SUM(shared_blks_written) ,
SUM(local_blks_hit) , SUM(local_blks_read) , SUM(local_blks_dirtied) , SUM(local_blks_written) , SUM(temp_blks_read) , SUM(temp_blks_written) , SUM(blk_read_time) , SUM(blk_write_time)
FROM pg_stat_statements WHERE dbid=(SELECT oid from pg_database where datname=current_database() )
GROUP BY dbid
'
)
AS t
( dbid oid , calls bigint ,
total_time double precision ,
rows bigint , shared_blks_hit bigint , shared_blks_read bigint ,shared_blks_dirtied bigint ,shared_blks_written bigint ,
local_blks_hit bigint ,local_blks_read bigint , local_blks_dirtied bigint ,local_blks_written bigint ,
temp_blks_read bigint ,temp_blks_written bigint ,
blk_read_time double precision , blk_write_time double precision
);
INSERT INTO pg_stat_history
(
snapshot_timestamp ,database_id ,
dbid , calls ,total_time ,
rows ,shared_blks_hit ,shared_blks_read ,shared_blks_dirtied ,shared_blks_written ,local_blks_hit ,
local_blks_read,local_blks_dirtied,local_blks_written,temp_blks_read,temp_blks_written,
blk_read_time, blk_write_time
)
VALUES
(
current_snapshot_timestamp ,
database_rec.id ,
pg_stat_snapshot.dbid ,pg_stat_snapshot.calls,
pg_stat_snapshot.total_time,
pg_stat_snapshot.rows ,pg_stat_snapshot.shared_blks_hit ,pg_stat_snapshot.shared_blks_read ,pg_stat_snapshot.shared_blks_dirtied ,pg_stat_snapshot.shared_blks_written ,
pg_stat_snapshot.local_blks_hit , pg_stat_snapshot.local_blks_read , pg_stat_snapshot.local_blks_dirtied , pg_stat_snapshot.local_blks_written ,
pg_stat_snapshot.temp_blks_read , pg_stat_snapshot.temp_blks_written , pg_stat_snapshot.blk_read_time , pg_stat_snapshot.blk_write_time
);
RAISE NOTICE 'Stvaranje snimka pg_stat_statements za upite sa min_time većim od 1000ms';
FOR pg_stat_snapshot IN
--Svi upiti sa max_time većim od 1000 ms
SELECT
*
FROM dblink('LINK1',
'SELECT
dbid , userid ,queryid,query,calls,total_time,min_time ,max_time,mean_time, stddev_time ,rows ,shared_blks_hit ,
shared_blks_read ,shared_blks_dirtied ,shared_blks_written ,
local_blks_hit , local_blks_read , local_blks_dirtied ,
local_blks_written , temp_blks_read , temp_blks_written , blk_read_time ,
blk_write_time
FROM pg_stat_statements
WHERE dbid=(SELECT oid from pg_database where datname=current_database() AND min_time >= 1000 )
'
)
AS t
( dbid oid , userid oid , queryid bigint ,query text , calls bigint ,
total_time double precision ,min_time double precision ,max_time double precision , mean_time double precision , stddev_time double precision ,
rows bigint , shared_blks_hit bigint , shared_blks_read bigint ,shared_blks_dirtied bigint ,shared_blks_written bigint ,
local_blks_hit bigint ,local_blks_read bigint , local_blks_dirtied bigint ,local_blks_written bigint ,
temp_blks_read bigint ,temp_blks_written bigint ,
blk_read_time double precision , blk_write_time double precision
)
LOOP
INSERT INTO pg_stat_history
(
snapshot_timestamp ,database_id ,
dbid ,userid , queryid , query , calls ,total_time ,min_time ,max_time ,mean_time ,stddev_time ,
rows ,shared_blks_hit ,shared_blks_read ,shared_blks_dirtied ,shared_blks_written ,local_blks_hit ,
local_blks_read,local_blks_dirtied,local_blks_written,temp_blks_read,temp_blks_written,
blk_read_time, blk_write_time
)
VALUES
(
current_snapshot_timestamp ,
database_rec.id ,
pg_stat_snapshot.dbid ,pg_stat_snapshot.userid ,pg_stat_snapshot.queryid,pg_stat_snapshot.query,pg_stat_snapshot.calls,
pg_stat_snapshot.total_time,pg_stat_snapshot.min_time ,pg_stat_snapshot.max_time,pg_stat_snapshot.mean_time, pg_stat_snapshot.stddev_time ,
pg_stat_snapshot.rows ,pg_stat_snapshot.shared_blks_hit ,pg_stat_snapshot.shared_blks_read ,pg_stat_snapshot.shared_blks_dirtied ,pg_stat_snapshot.shared_blks_written ,
pg_stat_snapshot.local_blks_hit , pg_stat_snapshot.local_blks_read , pg_stat_snapshot.local_blks_dirtied , pg_stat_snapshot.local_blks_written ,
pg_stat_snapshot.temp_blks_read , pg_stat_snapshot.temp_blks_written , pg_stat_snapshot.blk_read_time , pg_stat_snapshot.blk_write_time
);
END LOOP;
PERFORM dblink_disconnect('LINK1');
END LOOP ;--FOR database_rec IN SELECT * FROM database WHERE endpoint_id = endpoint_rec.id
END LOOP;
RETURN TRUE;
END
$$ LANGUAGE plpgsql;Kao rezultat, nakon nekog vremenskog perioda u tabeli pg_stat_history imaćemo skup uzoraka sadržaja tabele pg_stat_statements ciljane baze podataka.
Sam izveštaj
Koristeći jednostavne upite, možemo dobiti prilično korisne i zanimljive izveštaje.
Agregirani podaci za dati vremenski period
Upit
SELECT
database_id ,
SUM(calls) AS calls ,SUM(total_time) AS total_time ,
SUM(rows) AS rows , SUM(shared_blks_hit) AS shared_blks_hit,
SUM(shared_blks_read) AS shared_blks_read ,
SUM(shared_blks_dirtied) AS shared_blks_dirtied,
SUM(shared_blks_written) AS shared_blks_written ,
SUM(local_blks_hit) AS local_blks_hit ,
SUM(local_blks_read) AS local_blks_read ,
SUM(local_blks_dirtied) AS local_blks_dirtied ,
SUM(local_blks_written) AS local_blks_written,
SUM(temp_blks_read) AS temp_blks_read,
SUM(temp_blks_written) temp_blks_written ,
SUM(blk_read_time) AS blk_read_time ,
SUM(blk_write_time) AS blk_write_time
FROM
pg_stat_history
WHERE
queryid IS NULL AND
database_id = DATABASE_ID AND
snapshot_timestamp BETWEEN BEGIN_TIMEPOINT AND END_TIMEPOINT
GROUP BY database_id ;DB Vreme
to_char(interval '1 millisecond' * pg_total_stat_history_rec.total_time, 'HH24:MI:SS.MS')
I/O Vreme
to_char(interval '1 millisecond' * ( pg_total_stat_history_rec.blk_read_time + pg_total_stat_history_rec.blk_write_time ), 'HH24:MI:SS.MS')
TOP10 SQL po ukupnom vremenu
Upit
SELECT
queryid ,
SUM(calls) AS calls ,
SUM(total_time) AS total_time
FROM
pg_stat_history
WHERE
queryid IS NOT NULL AND
database_id = DATABASE_ID AND
snapshot_timestamp BETWEEN BEGIN_TIMEPOINT AND END_TIMEPOINT
GROUP BY queryid
ORDER BY 3 DESC
LIMIT 10------------------------------------------------------------------------------------- | TOP10 SQL PO UKUPNOJ VREMENU IZVRŠENJA | #| queryid| calls| procenat poziva| ukupno vreme (ms) | procenat dbvremena +----+-----------+-----------+-----------+--------------------------------+---------- | 1| 821760255| 2| .00001|00:03:23.141( 203141.681 ms.)| 5.42 | 2| 4152624390| 2| .00001|00:03:13.929( 193929.215 ms.)| 5.17 | 3| 1484454471| 4| .00001|00:02:09.129( 129129.057 ms.)| 3.44 | 4| 655729273| 1| .00000|00:02:01.869( 121869.981 ms.)| 3.25 | 5| 2460318461| 1| .00000|00:01:33.113( 93113.835 ms.)| 2.48 | 6| 2194493487| 4| .00001|00:00:17.377( 17377.868 ms.)| .46 | 7| 1053044345| 1| .00000|00:00:06.156( 6156.352 ms.)| .16 | 8| 3644780286| 1| .00000|00:00:01.063( 1063.830 ms.)| .03
TOP10 SQL po ukupnom I/O vremenu
Upit
SELECT
queryid ,
SUM(calls) AS calls ,
SUM(blk_read_time + blk_write_time) AS io_time
FROM
pg_stat_history
WHERE
queryid IS NOT NULL AND
database_id = DATABASE_ID AND
snapshot_timestamp BETWEEN BEGIN_TIMEPOINT AND END_TIMEPOINT
GROUP BY queryid
ORDER BY 3 DESC
LIMIT 10---------------------------------------------------------------------------------------- | TOP10 SQL PO UKUPNOM VREMENU I/O | #| queryid| pozivi| % poziva| Vreme I/O (ms)|% vremena db I/O +----+-----------+-----------+-----------+--------------------------------+------------- | 1| 4152624390| 2| .00001|00:08:31.616( 511616.592 ms.)| 31.06 | 2| 821760255| 2| .00001|00:08:27.099( 507099.036 ms.)| 30.78 | 3| 655729273| 1| .00000|00:05:02.209( 302209.137 ms.)| 18.35 | 4| 2460318461| 1| .00000|00:04:05.981( 245981.117 ms.)| 14.93 | 5| 1484454471| 4| .00001|00:00:39.144( 39144.221 ms.)| 2.38 | 6| 2194493487| 4| .00001|00:00:18.182( 18182.816 ms.)| 1.10 | 7| 1053044345| 1| .00000|00:00:16.611( 16611.722 ms.)| 1.01 | 8| 3644780286| 1| .00000|00:00:00.436( 436.205 ms.)| .03
TOP10 SQL po maksimalnom vremenu izvršenja
Upit
SELECT
id AS snapshotid ,
queryid ,
snapshot_timestamp ,
max_time
FROM
pg_stat_history
WHERE
queryid IS NOT NULL AND
database_id = DATABASE_ID AND
snapshot_timestamp BETWEEN BEGIN_TIMEPOINT AND END_TIMEPOINT
ORDER BY 4 DESC
LIMIT 10----------------------------------------------------------------------------------------- | TOP10 SQL PO MAKSMALNOM VREMENU IZVRŠENJA | #| snapshot| snapshotID| queryid| max_time (ms) +----+------------------+-----------+-----------+---------------------------------------- | 1| 05.04.2019 01:03| 4169| 655729273| 00:02:01.869( 121869.981 ms.) | 2| 04.04.2019 17:00| 4153| 821760255| 00:01:41.570( 101570.841 ms.) | 3| 04.04.2019 16:00| 4146| 821760255| 00:01:41.570( 101570.841 ms.) | 4| 04.04.2019 16:00| 4144| 4152624390| 00:01:36.964( 96964.607 ms.) | 5| 04.04.2019 17:00| 4151| 4152624390| 00:01:36.964( 96964.607 ms.) | 6| 05.04.2019 10:00| 4188| 1484454471| 00:01:33.452( 93452.150 ms.) | 7| 04.04.2019 17:00| 4150| 2460318461| 00:01:33.113( 93113.835 ms.) | 8| 04.04.2019 15:00| 4140| 1484454471| 00:00:11.892( 11892.302 ms.) | 9| 04.04.2019 16:00| 4145| 1484454471| 00:00:11.892( 11892.302 ms.) | 10| 04.04.2019 17:00| 4152| 1484454471| 00:00:11.892( 11892.302 ms.)
TOP10 SQL po DELJENOM čitanju/pisanu bafera
Upit
SELECT
id AS snapshotid ,
queryid ,
snapshot_timestamp ,
shared_blks_read ,
shared_blks_written
FROM
pg_stat_history
WHERE
queryid IS NOT NULL AND
database_id = DATABASE_ID AND
snapshot_timestamp BETWEEN BEGIN_TIMEPOINT AND END_TIMEPOINT AND
( shared_blks_read > 0 OR shared_blks_written > 0 )
ORDER BY 4 DESC , 5 DESC
LIMIT 10-------------------------------------------------------------------------------------------- | TOP10 SQL PO DELJENOM BUFERSKOM ČITANJU/PIŠU | #| snapshot| snapshotID| queryid| deljeni blokovi čitana| deljeni blokovi pisanja +----+------------------+-----------+-----------+---------------------+--------------------- | 1| 04.04.2019 17:00| 4153| 821760255| 797308| 0 | 2| 04.04.2019 16:00| 4146| 821760255| 797308| 0 | 3| 05.04.2019 01:03| 4169| 655729273| 797158| 0 | 4| 04.04.2019 16:00| 4144| 4152624390| 756514| 0 | 5| 04.04.2019 17:00| 4151| 4152624390| 756514| 0 | 6| 04.04.2019 17:00| 4150| 2460318461| 734117| 0 | 7| 04.04.2019 17:00| 4155| 3644780286| 52973| 0 | 8| 05.04.2019 01:03| 4168| 1053044345| 52818| 0 | 9| 04.04.2019 15:00| 4141| 2194493487| 52813| 0 | 10| 04.04.2019 16:00| 4147| 2194493487| 52813| 0 --------------------------------------------------------------------------------------------
Histogram distribucije upita po maksimalnom vremenu izvršavanja
Upiti
SELECT
MIN(max_time) AS hist_min ,
MAX(max_time) AS hist_max ,
(( MAX(max_time) - MIN(min_time) ) / hist_columns ) as hist_width
FROM
pg_stat_history
WHERE
queryid IS NOT NULL AND
database_id = DATABASE_ID AND
snapshot_timestamp BETWEEN BEGIN_TIMEPOINT AND END_TIMEPOINT ;
SELECT
SUM(calls) AS calls
FROM
pg_stat_history
WHERE
queryid IS NOT NULL AND
database_id =DATABASE_ID AND
snapshot_timestamp BETWEEN BEGIN_TIMEPOINT AND END_TIMEPOINT AND
( max_time >= hist_current_min AND max_time < hist_current_max ) ;
|----------------------------------------------------------------------------------------------- | MAX_TIME HISTOGRAM | UKUPNO POZIVA : 33851920 | MIN VREME : 00:00:01.063 | MAX VREME : 00:02:01.869 --------------------------------------------------------------------------------- | min trajanje| max trajanje| pozivi +----------------------------------+----------------------------------+---------- | 00:00:01.063( 1063.830 ms.) | 00:00:13.144( 13144.445 ms.) | 9 | 00:00:13.144( 13144.445 ms.) | 00:00:25.225( 25225.060 ms.) | 0 | 00:00:25.225( 25225.060 ms.) | 00:00:37.305( 37305.675 ms.) | 0 | 00:00:37.305( 37305.675 ms.) | 00:00:49.386( 49386.290 ms.) | 0 | 00:00:49.386( 49386.290 ms.) | 00:01:01.466( 61466.906 ms.) | 0 | 00:01:01.466( 61466.906 ms.) | 00:01:13.547( 73547.521 ms.) | 0 | 00:01:13.547( 73547.521 ms.) | 00:01:25.628( 85628.136 ms.) | 0 | 00:01:25.628( 85628.136 ms.) | 00:01:37.708( 97708.751 ms.) | 4 | 00:01:37.708( 97708.751 ms.) | 00:01:49.789( 109789.366 ms.) | 2 | 00:01:49.789( 109789.366 ms.) | 00:02:01.869( 121869.981 ms.) | 0
TOP10 Snapsotova po Upitu po Sekundi
Upiti
--pg_qps.sql
--Izračunaj Upite Po Sekundi
CREATE OR REPLACE FUNCTION pg_qps( pg_stat_history_id integer ) RETURNS double precision AS $$
DECLARE
pg_stat_history_rec record ;
prev_pg_stat_history_id integer ;
prev_pg_stat_history_rec record;
total_seconds double precision ;
result double precision;
BEGIN
result = 0 ;
SELECT *
INTO pg_stat_history_rec
FROM
pg_stat_history
WHERE id = pg_stat_history_id ;
IF pg_stat_history_rec.snapshot_timestamp IS NULL
THEN
RAISE EXCEPTION 'GRESKA - Nije pronađena pg_stat_history za id = %',pg_stat_history_id;
END IF ;
--RAISE NOTICE 'pg_stat_history_id = % , snapshot_timestamp = %', pg_stat_history_id ,
pg_stat_history_rec.snapshot_timestamp ;
SELECT
MAX(id)
INTO
prev_pg_stat_history_id
FROM
pg_stat_history
WHERE
database_id = pg_stat_history_rec.database_id AND
queryid IS NULL AND
id 0
THEN
result = pg_stat_history_rec.calls / total_seconds ;
ELSE
result = 0 ;
END IF;
RETURN result ;
END
$$ LANGUAGE plpgsql;
SELECT
id ,
snapshot_timestamp ,
calls ,
total_time ,
( select pg_qps( id )) AS QPS ,
blk_read_time ,
blk_write_time
FROM
pg_stat_history
WHERE
queryid IS NULL AND
database_id = DATABASE_ID AND
snapshot_timestamp BETWEEN BEGIN_TIMEPOINT AND END_TIMEPOINT AND
( select pg_qps( id )) IS NOT NULL
ORDER BY 5 DESC
LIMIT 10
|----------------------------------------------------------------------------------------------- | TOP10 Snimci poredani po broju upita po sekundi ----------------------------------------------------------------------------------------------------------------------------------------------- | #| snimak| snimakID| pozivi| ukupno vreme u bazi| QPS| I/O vreme| I/O vreme % +-----+------------------+-----------+-----------+----------------------------------+-----------+----------------------------------+----------- | 1| 04.04.2019 20:04| 4161| 5758631| 00:06:30.513( 390513.926 ms.)| 1573.396| 00:00:01.470( 1470.110 ms.)| .376 | 2| 04.04.2019 17:00| 4149| 3529197| 00:11:48.830( 708830.618 ms.)| 980.332| 00:12:47.834( 767834.052 ms.)| 108.324 | 3| 04.04.2019 16:00| 4143| 3525360| 00:10:13.492( 613492.351 ms.)| 979.267| 00:08:41.396( 521396.555 ms.)| 84.988 | 4| 04.04.2019 21:03| 4163| 2781536| 00:03:06.470( 186470.979 ms.)| 785.745| 00:00:00.249( 249.865 ms.)| .134 | 5| 04.04.2019 19:03| 4159| 2890362| 00:03:16.784( 196784.755 ms.)| 776.979| 00:00:01.441( 1441.386 ms.)| .732 | 6| 04.04.2019 14:00| 4137| 2397326| 00:04:43.033( 283033.854 ms.)| 665.924| 00:00:00.024( 24.505 ms.)| .009 | 7| 04.04.2019 15:00| 4139| 2394416| 00:04:51.435( 291435.010 ms.)| 665.116| 00:00:12.025( 12025.895 ms.)| 4.126 | 8| 04.04.2019 13:00| 4135| 2373043| 00:04:26.791( 266791.988 ms.)| 659.179| 00:00:00.064( 64.261 ms.)| .024 | 9| 05.04.2019 01:03| 4167| 4387191| 00:06:51.380( 411380.293 ms.)| 609.332| 00:05:18.847( 318847.407 ms.)| 77.507 | 10| 04.04.2019 18:01| 4157| 1145596| 00:01:19.217( 79217.372 ms.)| 313.004| 00:00:01.319( 1319.676 ms.)| 1.666
Historiya izvršenja po satu sa brojem upita po sekundi i vremenom I/O
Upit
SELECT
id ,
vreme_snimanja ,
pozivi ,
ukupno_vreme ,
( select pg_qps( id )) AS QPS ,
vreme_čitanja_blk ,
vreme_pisanja_blk
FROM
pg_stat_history
WHERE
queryid IS NULL AND
database_id = DATABASE_ID AND
vreme_snimanja BETWEEN BEGIN_TIMEPOINT AND END_TIMEPOINT
ORDER BY 2
|----------------------------------------------------------------------------------------------- | HISTORIJA IZVRŠAVANJA NA SAT SA QueryPerSeconds i I/O Vremenom ----------------------------------------------------------------------------------------------------------------------------------------------- | HISTORIJA UPITA PO SEKUNDI | #| trenutna slika| IDsnapshot| pozivi| ukupno dbvrijeme| QPS| I/O vreme| I/O vreme % +-----+------------------+-----------+-----------+----------------------------------+-----------+----------------------------------+----------- | 1| 04.04.2019 11:00| 4131| 3747| 00:00:00.835( 835.374 ms.)| 1.041| 00:00:00.000( .000 ms.)| .000 | 2| 04.04.2019 12:00| 4133| 1002722| 00:01:52.419( 112419.376 ms.)| 278.534| 00:00:00.149( 149.105 ms.)| .133 | 3| 04.04.2019 13:00| 4135| 2373043| 00:04:26.791( 266791.988 ms.)| 659.179| 00:00:00.064( 64.261 ms.)| .024 | 4| 04.04.2019 14:00| 4137| 2397326| 00:04:43.033( 283033.854 ms.)| 665.924| 00:00:00.024( 24.505 ms.)| .009 | 5| 04.04.2019 15:00| 4139| 2394416| 00:04:51.435( 291435.010 ms.)| 665.116| 00:00:12.025( 12025.895 ms.)| 4.126 | 6| 04.04.2019 16:00| 4143| 3525360| 00:10:13.492( 613492.351 ms.)| 979.267| 00:08:41.396( 521396.555 ms.)| 84.988 | 7| 04.04.2019 17:00| 4149| 3529197| 00:11:48.830( 708830.618 ms.)| 980.332| 00:12:47.834( 767834.052 ms.)| 108.324 | 8| 04.04.2019 18:01| 4157| 1145596| 00:01:19.217( 79217.372 ms.)| 313.004| 00:00:01.319( 1319.676 ms.)| 1.666 | 9| 04.04.2019 19:03| 4159| 2890362| 00:03:16.784( 196784.755 ms.)| 776.979| 00:00:01.441( 1441.386 ms.)| .732 | 10| 04.04.2019 20:04| 4161| 5758631| 00:06:30.513( 390513.926 ms.)| 1573.396| 00:00:01.470( 1470.110 ms.)| .376 | 11| 04.04.2019 21:03| 4163| 2781536| 00:03:06.470( 186470.979 ms.)| 785.745| 00:00:00.249( 249.865 ms.)| .134 | 12| 04.04.2019 23:03| 4165| 1443155| 00:01:34.467( 94467.539 ms.)| 200.438| 00:00:00.015( 15.287 ms.)| .016 | 13| 05.04.2019 01:03| 4167| 4387191| 00:06:51.380( 411380.293 ms.)| 609.332| 00:05:18.847( 318847.407 ms.)| 77.507 | 14| 05.04.2019 02:03| 4171| 189852| 00:00:10.989( 10989.899 ms.)| 52.737| 00:00:00.539( 539.110 ms.)| 4.906 | 15| 05.04.2019 03:01| 4173| 3627| 00:00:00.103( 103.000 ms.)| 1.042| 00:00:00.004( 4.131 ms.)| 4.010 | 16| 05.04.2019 04:00| 4175| 3627| 00:00:00.085( 85.235 ms.)| 1.025| 00:00:00.003( 3.811 ms.)| 4.471 | 17| 05.04.2019 05:00| 4177| 3747| 00:00:00.849( 849.454 ms.)| 1.041| 00:00:00.006( 6.124 ms.)| .721 | 18| 05.04.2019 06:00| 4179| 3747| 00:00:00.849( 849.561 ms.)| 1.041| 00:00:00.000( .051 ms.)| .006 | 19| 05.04.2019 07:00| 4181| 3747| 00:00:00.839( 839.416 ms.)| 1.041| 00:00:00.000( .062 ms.)| .007 | 20| 05.04.2019 08:00| 4183| 3747| 00:00:00.846( 846.382 ms.)| 1.041| 00:00:00.000( .007 ms.)| .001 | 21| 05.04.2019 09:00| 4185| 3747| 00:00:00.855( 855.426 ms.)| 1.041| 00:00:00.000( .065 ms.)| .008 | 22| 05.04.2019 10:00| 4187| 3797| 00:01:40.150( 100150.165 ms.)| 1.055| 00:00:21.845( 21845.217 ms.)| 21.812
Tekst svih SQL-izbora
Upit
SELECT
queryid ,
query
FROM
pg_stat_history
WHERE
queryid IS NOT NULL AND
database_id = DATABASE_ID AND
snapshot_timestamp BETWEEN BEGIN_TIMEPOINT AND END_TIMEPOINT
GROUP BY queryid , query
Zaključak
Kao što se može vidjeti, prilično jednostavnim sredstvima, može se dobiti dosta korisnih informacija o opterećenju i stanju baze.
Napomena:Ako u upitima zabilježimo queryid, dobijamo historiju po pojedinačnom upitu (radi uštede prostora, izvještaji po pojedinačnom upitu su izostavljeni).
Dakle, statistički podaci o performansama upita — postoje i prikupljaju se.
Prva faza 'prikupljanje statističkih podataka' — završena.
Možemo preći na drugu fazu — 'podešavanje metrika performansi'.

Ali to je već sasvim druga priča.
Nastavak sledi…
Izvor: habr.com
