ProHoster > Блог > Gudanarwa > Kula da ayyuka na tambayoyin PostgreSQL. Kashi na 1 - rahoto

Kula da ayyuka na tambayoyin PostgreSQL. Kashi na 1 - rahoto

Injiniya - Fassara daga Latin - wahayi.
Injiniya na iya yin komai. (c) R. Diesel.
Epigraphs.
Kula da ayyuka na tambayoyin PostgreSQL. Kashi na 1 - rahoto
Ko labari game da dalilin da ya sa ma'aikacin bayanai ke buƙatar tunawa da shirye-shiryen da ya gabata.

Magana

An canza duk sunaye. Matches ba zato ba tsammani. Kayan shine ra'ayi na sirri na marubuci kawai.

Rashin yarda da garanti: a cikin jerin labaran da aka tsara ba za a sami cikakken cikakken bayani game da tebur da rubutun da aka yi amfani da su ba. Ba za a iya amfani da kayan nan da nan "AS IS".
Na farko, saboda yawan adadin kayan.
abu na biyu, saboda kaifi tare da samar da tushe na ainihin abokin ciniki.
Saboda haka, kawai ra'ayoyi da kwatanci a cikin mafi yawan nau'i na gaba ɗaya za a ba da su a cikin labaran.
Wataƙila a nan gaba tsarin zai girma zuwa matakin aikawa akan GitHub, ko watakila a'a. Lokaci zai nuna.

Farkon labarin-Kuna tuna yadda duk ya fara".
Abin da ya faru a sakamakon haka, a cikin mafi yawan sharuddan - "Haɗin kai azaman ɗayan hanyoyin haɓaka aikin PostgreSQL»

Me yasa nake buƙatar duk wannan?

To, da farko, don kada ku manta da kanku, tunawa da kwanakin ɗaukaka a cikin ritaya.
Na biyu, don tsara abin da aka rubuta. Don ni kaina, wani lokacin nakan fara ruɗe in manta sassa daban-daban.

To, kuma mafi mahimmanci - ba zato ba tsammani zai iya zama mai amfani ga wani kuma ya taimaka kada ya sake farfado da dabaran kuma kada ya tattara rake. A wasu kalmomi, inganta karma (ba Khabrovsky ba). Don mafi kyawun abu a wannan duniyar shine ra'ayoyi. Babban abu shine samun ra'ayi. Kuma don fassara ra'ayin zuwa gaskiya ya riga ya zama batun fasaha kawai.

Don haka mu fara a hankali...

Samar da matsala.

Akwai:

PostgreSQL(10.5), gauraye lodi (OLTP+DSS), matsakaici zuwa nauyi nauyi, wanda aka shirya a cikin girgijen AWS.
Babu saka idanu na bayanai, ana gabatar da sa ido kan ababen more rayuwa azaman daidaitattun kayan aikin AWS a cikin ƙaramin tsari.

An buƙata:

Saka idanu aiki da matsayi na ma'ajin bayanai, nemo kuma sami bayanan farko don inganta manyan tambayoyin bayanai.

Taƙaitaccen gabatarwa ko nazarin mafita

Da farko, bari mu yi ƙoƙari mu yi nazarin hanyoyin magance matsalar ta mahangar nazarin kwatancen fa’idodi da matsalolin da injiniyan ke fuskanta, sannan waɗanda ya kamata su kasance cikin jerin ma’aikatan su magance fa’ida da asara. na gudanarwa.

Zabin 1 - "Aiki akan buƙata"

Mu bar komai yadda yake. Idan abokin ciniki bai gamsu da wani abu ba a cikin lafiya, aikin bayanan bayanai ko aikace-aikacen, zai sanar da injiniyoyin DBA ta imel ko ta hanyar ƙirƙirar wani lamari a cikin akwatin tikiti.
Injiniya, da ya karɓi sanarwar, zai fahimci matsalar, ya ba da mafita, ko ya warware matsalar, yana fatan cewa komai zai warware kansa, kuma ta yaya, komai zai manta da shi.
Gingerbread da donuts, bruises da bumpsGingerbread da donuts:
1. Babu wani abu da za a yi
2. Koyaushe akwai damar fita da kazanta.
3. Yawancin lokaci da za ku iya kashewa da kanku.
Kumburi da kumburi:
1. Ba da dade ko ba dade, abokin ciniki zai yi tunani game da ainihin kasancewa da adalci na duniya a wannan duniyar kuma ya sake tambayar kansa tambaya - me yasa nake biyan su kuɗi na? Sakamakon ko da yaushe iri ɗaya ne - tambayar kawai ita ce lokacin da abokin ciniki ya gundura kuma ya yi bankwana da shi. Kuma feeder babu kowa. Abin bakin ciki ne.
2. Ci gaban injiniya sifili ne.
3. Wahala wajen tsara aiki da lodi

Zabin 2 - "Rawa tare da tambourine, saka da sanya takalma"

Sakin layi na 1-Me yasa muke buƙatar tsarin kulawa, za mu karɓi duk buƙatun. Muna ƙaddamar da gungun nau'ikan tambayoyi zuwa ƙamus na bayanai da ra'ayoyi masu ƙarfi, kunna kowane nau'in ƙididdiga, kawo komai cikin tebur, bincika jerin jeri da tebur lokaci-lokaci, kamar yadda yake. A sakamakon haka, muna da kyawawan hotuna, tebur, rahotanni. Babban abu - wannan zai zama ƙari, ƙari.
Sakin layi na 2-Samar da ayyuka-gudanar da bincike na duk wannan.
Sakin layi na 3-Muna shirya wani takarda, muna kiran wannan takarda, a sauƙaƙe - "yadda za mu samar da bayanan."
Sakin layi na 4- Abokin ciniki, ganin duk wannan girman zane-zane da adadi, yana cikin rashin amincewar yara - yanzu komai zai yi aiki a gare mu, nan ba da jimawa ba. Kuma, sauƙi da raɗaɗi tare da albarkatun kuɗin su. Gudanarwa kuma yana da tabbacin cewa injiniyoyinmu suna aiki tuƙuru. Matsakaicin lodi.
Sakin layi na 5- Maimaita mataki na 1 akai-akai.
Gingerbread da donuts, bruises da bumpsGingerbread da donuts:
1. Rayuwar manajoji da injiniyoyi suna da sauƙi, tsinkaya kuma cike da aiki. Komai yana ta hayaniya, kowa ya shagaltu.
2. Rayuwar abokin ciniki kuma ba ta da kyau - koyaushe yana da tabbacin cewa kana buƙatar yin haƙuri kaɗan kuma komai zai yi aiki. Ba samun lafiya ba, da kyau, da kyau - wannan duniyar ba ta da adalci, a rayuwa ta gaba - sa'a.
Kumburi da kumburi:
1. Ba dade ko ba jima, za a sami mai ba da sabis mai wayo na irin wannan sabis ɗin wanda zai yi abu ɗaya, amma kaɗan kaɗan. Kuma idan sakamakon ya kasance iri ɗaya, me yasa za ku biya ƙarin. Wanda kuma zai kai ga bacewar mai ciyarwa.
2. Yana da ban sha'awa. Yadda m kowane ɗan ƙaramin aiki mai ma'ana.
3. Kamar yadda a cikin sigar baya - babu ci gaba. Amma ga injiniya, abin da ya rage shine, ba kamar zaɓi na farko ba, a nan kana buƙatar samar da IDB akai-akai. Kuma hakan yana ɗaukar lokaci. Wanda za'a iya kashewa don amfanin masoyinka. Domin ba za ku iya kula da kanku ba, kowa ya damu da ku.

Zabin 3-Babu buqatar qirqirar keke, kana buqatar siya ka hau.

Injiniyoyi daga wasu kamfanoni suna sane suna cin pizza tare da giya (oh, lokutan ɗaukaka na St. Petersburg a cikin 90s). Bari mu yi amfani da tsarin sa ido waɗanda aka yi, gyarawa da aiki, kuma gabaɗaya magana, suna kawo fa'idodi (da kyau, aƙalla ga mahaliccinsu).
Gingerbread da donuts, bruises da bumpsGingerbread da donuts:
1. Babu buƙatar bata lokaci wajen ƙirƙira abin da aka riga aka ƙirƙira. Dauke da amfani.
2. Tsarin sa ido ba wawaye suke rubutawa ba, kuma ba shakka suna da amfani.
3. Tsarukan sa ido na aiki yawanci suna ba da bayanan tacewa masu amfani.
Kumburi da kumburi:
1. Injiniya a wannan yanayin ba injiniya bane, amma mai amfani da kayan wani ne kawai.
2. Dole ne abokin ciniki ya gamsu da bukatar sayan wani abu wanda gaba daya baya son fahimta, kuma bai kamata ba, kuma gaba daya an amince da kasafin kudin shekara kuma ba zai canza ba. Sannan kuna buƙatar ware wata hanya daban, saita shi don takamaiman tsari. Wadancan. Da farko kuna buƙatar biya, biya kuma ku sake biya. Kuma abokin ciniki yana da rowa. Wannan ita ce ka'ida ta wannan rayuwar.

Abin da ya yi, Chernyshevsky? Tambayar ku tana da mahimmanci. (Tare da)

A cikin wannan yanayin musamman da halin da ake ciki yanzu, zaku iya yin ɗan daban - mu yi namu tsarin sa ido.
Kula da ayyuka na tambayoyin PostgreSQL. Kashi na 1 - rahoto
To, ba tsarin ba, ba shakka, a cikin cikakkiyar ma'anar kalmar, wannan yana da ƙarfi da girman kai, amma aƙalla ko ta yaya ya sauƙaƙe wa kanku da tattara ƙarin bayani don warware abubuwan da suka faru. Don kada ku sami kanku a cikin yanayi - "je can, ban san inda ba, nemo wannan, ban san menene ba."

Menene fa'idodi da rashin amfanin wannan zaɓi:

Sakamakon:
1. Yana da ban sha'awa. Da kyau, aƙalla ya fi ban sha'awa fiye da akai-akai "rufe fayilolin bayanai, canza sararin tebur, da sauransu."
2. Waɗannan sababbin ƙwarewa ne da sababbin ci gaba. Wanda a nan gaba ba dade ko ba dade zai ba da gingerbread da ya cancanta da kyau.
Fursunoni:
1. Dole a yi aiki. Yi aiki da yawa.
2. Dole ne ku yi bayani akai-akai akan ma'ana da hangen nesa na kowane aiki.
3. Dole ne a yi hadaya da wani abu, saboda kawai albarkatun da injiniyan ke da shi - lokaci - yana iyakance ta Duniya.
4. Mafi muni kuma mafi rashin jin daɗi - a sakamakon haka, datti kamar "Ba linzamin kwamfuta ba, ba kwaɗo ba, amma dabbar da ba a sani ba" na iya fitowa.

Wanda ba ya hadarin wani abu ba ya sha shampagne.
Don haka, jin daɗi ya fara.

Babban ra'ayi - makirci

Kula da ayyuka na tambayoyin PostgreSQL. Kashi na 1 - rahoto
(Misalin da aka ɗauka daga labarin «Haɗin kai azaman ɗayan hanyoyin haɓaka aikin PostgreSQL»)

Bayani:

  • An shigar da bayanan da aka yi niyya tare da daidaitaccen tsawo na PostgreSQL "pg_stat_statements".
  • A cikin bayanan sa ido, mun ƙirƙiri saitin tebur sabis don adana tarihin pg_stat_statements a matakin farko kuma don daidaita ma'auni da saka idanu a gaba.
  • A kan mai saka idanu, muna ƙirƙirar saitin rubutun bash, gami da waɗanda ke haifar da al'amura a cikin tsarin tikitin.

Teburan sabis

Don farawa da, ERD mai sauƙaƙan tsari, abin da ya faru a ƙarshe:
Kula da ayyuka na tambayoyin PostgreSQL. Kashi na 1 - rahoto
Taƙaitaccen bayanin teburƙarshe - mai masaukin baki, alamar haɗi zuwa misali
database - zažužžukan database
pg_stat_history - Teburin tarihi don adana hotunan ɗan lokaci na pg_stat_statements ra'ayin bayanan da aka yi niyya
metric_kamus - Kamus na ma'aunin aiki
metric_config - daidaita ma'auni guda ɗaya
awo - takamaiman ma'auni don buƙatar da ake sa ido
metric_alert_history - tarihin gargadin aiki
log_query - Teburin sabis don adana bayanan da aka tantance daga fayil ɗin log ɗin PostgreSQL da aka sauke daga AWS
tushe - sigogi na lokacin lokacin da aka yi amfani da su azaman tushe
wurin dubawa - daidaita ma'auni don duba matsayin ma'ajin bayanai
checkpoint_alert_history - tarihin faɗakarwa na ma'aunin binciken matsayin bayanai
pg_stat_db_queries - tebur sabis na buƙatun aiki
aiki_log - tebur sabis log log
tarkon_oid - teburin sabis na sanyi na tarko

Mataki na 1 - tattara kididdigar aiki da samun rahotanni

Ana amfani da tebur don adana bayanan ƙididdiga. pg_stat_history
pg_stat_history tsarin tebur

                                          Tebur "jama'a.pg_stat_history" Shagon | irin | Masu gyara--------------- ------------------ id | lamba | ba maras kyau ba nextval('pg_stat_history_id_seq'::regclass) snapshot_timestamp | timestamp ba tare da yanki lokaci | database_id | lamba | dbid | irin | mai amfani | irin | tambaya | babba | tambaya | rubutu | kira | babba | jimlar_lokaci | daidaito biyu | min_lokaci | daidaito biyu | max_lokaci | daidaito biyu | lokaci_lokaci | daidaito biyu | stddev_lokaci | daidaito biyu | layuka | babba | shared_blks_buga | babba | shared_blks_karatu | babba | shared_blks_datti | babba | shared_blks_ rubuta | babba | local_blks_hit | babba | local_blks_read | babba | local_blks_dirtied | babba | local_blks_ rubuta | babba | temp_blks_karanta | babba | temp_blks_ rubuta | babba | blk_karanta_lokaci | daidaito biyu | blk_rubuta_lokaci | daidaito biyu | baseline_id | lamba | Fihirisa: "pg_stat_history_pkey" PRIMARY KEY, btree (id) "database_idx" btree (database_id) "queryid_idx" btree (queryid) "snapshot_timestamp_idx" btree (snapshot_timestamp) Ƙuntataccen maɓalli na waje (EYFID) KYAUTATA maɓalli na waje: "Bayanai_RENCES" database (id ) AKAN Goge CASCADE

Kamar yadda kuke gani, tebur ɗin bayanan duba ne kawai pg_stat_bayani a cikin manufa database.

Amfani da wannan tebur yana da sauqi qwarai.

pg_stat_history zai wakilci tara ƙididdiga na aiwatar da tambaya na kowace awa. A farkon kowace sa'a, bayan cika tebur, ƙididdiga pg_stat_bayani sake saita da pg_stat_statements_sake saitin().
Note: Ana tattara ƙididdiga don buƙatun tare da tsawon fiye da daƙiƙa 1.
Yawaita teburin 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 'NEW SHAPSHOT IS CREATING';
		
		--Connect to the target DB	  
	    EXECUTE 'SELECT dblink_connect(''LINK1'',''host='||endpoint_rec.host||' dbname='||database_rec.name||' user=USER password=PASSWORD '')';
 
        RAISE NOTICE 'host % and dbname % ',endpoint_rec.host,database_rec.name;
		RAISE NOTICE 'Creating snapshot of pg_stat_statements for database %',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 'Creating snapshot of pg_stat_statements for queries with min_time more than 1000ms';
	
        FOR pg_stat_snapshot IN
          --All queries with max_time greater than 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;

A sakamakon haka, bayan wani lokaci a cikin tebur pg_stat_history za mu sami saitin hotuna na abubuwan da ke cikin tebur pg_stat_bayani manufa database.

Ainihin rahoto

Yin amfani da tambayoyi masu sauƙi, zaku iya samun rahotanni masu amfani da ban sha'awa.

Haɗaɗɗen bayanai na ɗan lokaci

Nemi

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 ;

D.B lokaci

to_char(tazara '1 millise seconds' * pg_total_stat_history_rec.total_time, 'HH24: MI: SS.MS')

Lokacin I/O

to_char (tazara '1 millise seconds' * ( pg_total_stat_history_rec.blk_read_time + pg_total_stat_history_rec.blk_write_time), 'HH24: MI: SS.MS')

TOP10 SQL ta jimlar_lokaci

Nemi

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 BY JAMA'AR LOKACIN KIYAYEWA | #| tambaya | kira| kira% | jimlar_lokaci (ms) | dbtime% +---+--------------------------- ------------------------------ | 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 ta jimlar lokacin I/O

Nemi

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 BY TOTAL I/O LOKACI | #| tambaya | kira| kira% | Lokacin I/O (ms)|db I/O lokacin % +----+------------------------+--- -------------------------------------------------- -- | 1| 4152624390| 2| .00001|00:08:31.616( 511616.592 ms.)| Yuni 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 ta max lokacin aiwatarwa

Nemi

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 BY MAX LOKACIN FIYASA | #| hotuna | snapshotID| tambaya | max_time (ms) +----+---------- --+------------------------------------------------ | 1| 05.04.2019/01/03 4169:655729273| 00| 02| 01.869: 121869.981: 2 (04.04.2019 ms.) | 17| 00/4153/821760255 00:01| 41.570| 101570.841| 3:04.04.2019:16 (00 ms.) | 4146| 821760255/00/01 41.570:101570.841| 4| 04.04.2019| 16:00:4144 (4152624390 ms.) | 00| 01/36.964/96964.607 5:04.04.2019| 17| 00| 4151: 4152624390: 00 ( 01 ms.) | 36.964| 96964.607/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: 8 ( 04.04.2019 ms.) | 15| 00/4140/1484454471 00:00| 11.892| 11892.302| 9: 04.04.2019: 16 ( 00 ms.) | 4145| 1484454471/00/00 11.892:11892.302| 10| 04.04.2019| 17:00:4152 (1484454471 ms.) | 00| 00/11.892/11892.302 XNUMX:XNUMX| XNUMX| XNUMX| XNUMX:XNUMX:XNUMX (XNUMX ms.) | XNUMX| XNUMX/XNUMX/XNUMX XNUMX:XNUMX| XNUMX| XNUMX| XNUMX:XNUMX:XNUMX (XNUMX ms.)

TOP10 SQL ta SHARED buffer karanta/rubuta

Nemi

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 BY SHARE BUFFER KARANTA/RUBUTA | #| hotuna | snapshotID| tambaya | tubalan rabawa karanta| Rubuce-rubucen da aka raba----+----------- --------------------------------------------------- | 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 | XNUMX| XNUMX/XNUMX/XNUMX XNUMX:XNUMX| XNUMX| XNUMX| XNUMX| XNUMX | XNUMX| XNUMX/XNUMX/XNUMX XNUMX:XNUMX| XNUMX| XNUMX| XNUMX| XNUMX ------------------------------------------------- -------------------------------------------------

Histogram na rarraba tambaya ta iyakar lokacin aiwatarwa

Bukatu

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 | JAMA'AR KIRAN: 33851920 | LOKACI : 00:00:01.063 | MAX LOKACI : 00:02:01.869 --------------------------------------------------- ------------------------ | min duration| max duration| kira +------------------------------------------------- ----------------- | 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 Snapshots ta Tambaya a cikin dakika

Bukatu

--pg_qps.sql
--Calculate Query Per Second 
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 'ERROR - Not found pg_stat_history for 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 < pg_stat_history_rec.id ;

  IF prev_pg_stat_history_id IS NULL 
  THEN
    RAISE NOTICE 'Not found previous pg_stat_history shapshot for id = %',pg_stat_history_id;
	RETURN NULL ;
  END IF;
  
  SELECT *
  INTO prev_pg_stat_history_rec
  FROM 
    pg_stat_history
  WHERE id = prev_pg_stat_history_id ;
  
  --RAISE NOTICE 'prev_pg_stat_history_id = % , prev_snapshot_timestamp = %', prev_pg_stat_history_id , prev_pg_stat_history_rec.snapshot_timestamp ;    

  total_seconds = extract(epoch from ( pg_stat_history_rec.snapshot_timestamp - prev_pg_stat_history_rec.snapshot_timestamp ));
  
  --RAISE NOTICE 'total_seconds = % ', total_seconds ;    
  
  --RAISE NOTICE 'calls = % ', pg_stat_history_rec.calls ;      
  
  IF total_seconds > 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 Snapshots da aka yi oda ta lambobin QueryPerSeconds ----------------------------------------------------------------- ------------------------------------------------------------------ ------------------------------------------------- | #| hotuna | snapshotID| kira| jimlar dbtime| QPS | I/O lokaci | Lokacin I/O% +------------------------------------------------------- -------------------- --------------------------------------------- | 1| 04.04.2019/20/04 4161:5758631| 00| 06| 30.513:390513.926:1573.396(00 ms.)| 00| 01.470:1470.110:376 (2 ms.)| .04.04.2019 | 17| 00/4149/3529197 00:11| 48.830| 708830.618| 980.332:00:12( 47.834 ms.)| 767834.052| 108.324:3:04.04.2019( 16 ms.)| 00 | 4143| 3525360/00/10 13.492:613492.351| 979.267| 00| 08:41.396:521396.555( 84.988 ms.)| 4| 04.04.2019:21:03(4163 ms.)| 2781536 | 00| 03/06.470/186470.979 785.745:00| 00| 00.249| 249.865:134:5 (04.04.2019 ms.)| 19| 03:4159:2890362 (00 ms.)| .03 | 16.784| 196784.755/776.979/00 00:01.441| 1441.386| 732| 6:04.04.2019:14 (00 ms.)| 4137| 2397326:00:04 (43.033 ms.)| .283033.854 | 665.924| 00/00/00.024 24.505:009 | 7| 04.04.2019| 15:00:4139 (2394416 ms.)| 00| 04:51.435:291435.010 (665.116 ms.)| .00 | 00| 12.025/12025.895/4.126 8:04.04.2019| 13| 00| 4135:2373043:00(04 ms.)| 26.791| 266791.988:659.179:00 (00 ms.)| 00.064 | 64.261| 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:313.004 (00 ms.)| 00| 01.319:1319.676:1.666(XNUMX ms.)| XNUMX | XNUMX| XNUMX/XNUMX/XNUMX XNUMX:XNUMX| XNUMX| XNUMX| XNUMX:XNUMX:XNUMX ( XNUMX ms.)| XNUMX| XNUMX:XNUMX:XNUMX (XNUMX ms.)| XNUMX

Tarihin Kisa na Sa'a tare da QueryPerSeconds da Lokacin I/O

Nemi

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
ORDER BY 2

|-----------------------------------------------------------------------------------------------
| HOURLY EXECUTION HISTORY  WITH QueryPerSeconds and I/O Time
-----------------------------------------------------------------------------------------------------------------------------------------------
| QUERY PER SECOND HISTORY
|    #|          snapshot| snapshotID|      calls|                      total dbtime|        QPS|                          I/O time| I/O time %
+-----+------------------+-----------+-----------+----------------------------------+-----------+----------------------------------+-----------
|    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

Rubutun duk zaɓin SQL

Nemi

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

Sakamakon

Kamar yadda kake gani, ta hanyoyi masu sauƙi, za ka iya samun bayanai masu yawa masu amfani game da nauyin aiki da yanayin bayanan.

Lura:Idan kun gyara queryid a cikin tambayoyin, to, za mu sami tarihi don buƙatun daban (domin adana sarari, an cire rahotannin buƙatun daban).

Don haka, ana samun bayanan ƙididdiga akan aikin tambaya kuma ana tattara su.
An kammala matakin farko "tarin bayanan kididdiga".

Kuna iya ci gaba zuwa mataki na biyu - "daidaita ma'aunin aikin".
Kula da ayyuka na tambayoyin PostgreSQL. Kashi na 1 - rahoto

Amma wannan labari ne kwata-kwata.

A ci gaba…

source: www.habr.com

Add a comment