ProHoster > Блог > Gudanarwa > Ƙoƙarin ƙirƙirar analog na ASH don PostgreSQL

Ƙoƙarin ƙirƙirar analog na ASH don PostgreSQL

Tsara matsalar

Don inganta tambayoyin PostgreSQL, ikon yin nazarin tarihin ayyuka, musamman, jira, makullai, da kididdigar tebur, ana buƙata sosai.

Dama akwai

Kayan aikin Binciken Aiki na Tarihi ko "AWR don Postgres": bayani mai ban sha'awa sosai, amma babu tarihin pg_stat_activity da pg_locks.

pgsentinel tsawo :
«Duk bayanan da aka tara ana adana su ne kawai a cikin RAM, kuma adadin ƙwaƙwalwar da aka cinye ana sarrafa shi ta adadin bayanan da aka adana na ƙarshe.

An ƙara filin tambaya - tambaya iri ɗaya daga pg_stat_statements tsawo (wanda ake buƙatar shigarwa kafin shigarwa).«

Wannan, ba shakka, zai taimaka da yawa, amma abin da ya fi damuwa shi ne batu na farko. "Duk bayanan da aka tara ana adana su a cikin RAM kawai ”, i.e. akwai tasiri akan tushen manufa. Bugu da kari, babu tarihin kulle da kididdigar tebur. Wadancan. Maganin gabaɗaya yana magana bai cika ba: “Babu wani fakitin da aka shirya don shigarwa tukuna. Ana ba da shawarar zazzage tushen kuma tattara ɗakin karatu da kanku. Da farko kuna buƙatar shigar da kunshin “devel” don uwar garken ku kuma saita hanya zuwa pg_config a cikin madaidaicin PATH.".

Gabaɗaya, akwai damuwa mai yawa, kuma a cikin yanayin samar da bayanai masu mahimmanci, mai yiwuwa ba zai yiwu a yi wani abu tare da uwar garken ba. Muna bukatar mu sake fito da wani abu na kanmu.

Gargaɗi.

Saboda girman girma da yawa kuma saboda lokacin gwaji bai cika ba, labarin ya fi dacewa don dalilai na bayanai, maimakon saitin abubuwan da aka samu da sakamako na tsaka-tsaki.
Za a shirya ƙarin cikakkun bayanai daga baya, a cikin sassa

Bukatun daftarin aiki don mafita

Wajibi ne don haɓaka kayan aiki wanda zai ba ku damar adanawa:

pg_stat_activity duba tarihin
Tarihin kulle zaman ta amfani da duba pg_locks

Bukatar mafita– Rage tasiri akan bayanan da aka yi niyya.

Babban ra'ayi- an ƙaddamar da wakilin tattara bayanai ba a cikin bayanan da aka yi niyya ba, amma a cikin bayanan kulawa a matsayin sabis na tsarin. Ee, wasu asarar bayanai yana yiwuwa, amma wannan ba mahimmanci ba ne don bayar da rahoto, amma babu wani tasiri akan bayanan da aka yi niyya dangane da ƙwaƙwalwar ajiya da sararin diski. Kuma a cikin yanayin yin amfani da tafkin haɗin gwiwa, tasiri akan hanyoyin masu amfani yana da kadan.

Matakan aiwatarwa

1.Tables na sabis

Ana amfani da wani tsari daban don adana tebur, don kada a rikitar da nazarin manyan teburin da aka yi amfani da su.

DROP SCHEMA IF EXISTS activity_hist ;
CREATE SCHEMA activity_hist AUTHORIZATION monitor ;

Muhimmi: Ba a ƙirƙiri makircin a cikin bayanan da aka yi niyya ba, amma a cikin bayanan sa ido.

pg_stat_activity duba tarihin

Ana amfani da tebur don adana hotuna na yanzu na pg_stat_activity view

aiki_hist.history_pg_stat_aiki :

--ACTIVITY_HIST.HISTORY_PG_STAT_ACTIVITY
DROP TABLE IF EXISTS activity_hist.history_pg_stat_activity;
CREATE TABLE activity_hist.history_pg_stat_activity
(
  timepoint timestamp without time zone ,
  datid             oid  , 
  datname           name ,
  pid               integer,
  usesysid          oid    ,
  usename           name   ,
  application_name  text   ,
  client_addr       inet   ,
  client_hostname   text   ,
  client_port       integer,
  backend_start     timestamp with time zone ,
  xact_start        timestamp with time zone ,
  query_start       timestamp with time zone ,
  state_change      timestamp with time zone ,
  wait_event_type   text ,                     
  wait_event        text ,                   
  state             text ,                  
  backend_xid       xid  ,                 
  backend_xmin      xid  ,                
  query             text ,               
  backend_type      text ,  
  queryid           bigint
);

Don hanzarta shigarwa - babu fihirisa ko hani.

Don adana tarihin kanta, ana amfani da tebur da aka raba:

ayyuka_hist.archive_pg_stat_aiki :

DROP TABLE IF EXISTS activity_hist.archive_pg_stat_activity;
CREATE TABLE activity_hist.archive_pg_stat_activity
(
  timepoint timestamp without time zone ,
  datid             oid  , 
  datname           name ,
  pid               integer,
  usesysid          oid    ,
  usename           name   ,
  application_name  text   ,
  client_addr       inet   ,
  client_hostname   text   ,
  client_port       integer,
  backend_start     timestamp with time zone ,
  xact_start        timestamp with time zone ,
  query_start       timestamp with time zone ,
  state_change      timestamp with time zone ,
  wait_event_type   text ,                     
  wait_event        text ,                   
  state             text ,                  
  backend_xid       xid  ,                 
  backend_xmin      xid  ,                
  query             text ,               
  backend_type      text ,
  queryid           bigint
)
PARTITION BY RANGE (timepoint);

Tun da a cikin wannan yanayin babu buƙatun don saurin shigarwa, an ƙirƙiri wasu fihirisa don hanzarta ƙirƙirar rahotanni.

Tarihin toshe zaman

Ana amfani da tebur don adana hotuna na makullin zaman yanzu:

Ayyukan_hist.history_locking:

--ACTIVITY_HIST.HISTORY_LOCKING
DROP TABLE IF EXISTS activity_hist.history_locking;
CREATE TABLE activity_hist.history_locking
(
	timepoint timestamp without time zone ,
	locktype text ,
	relation oid ,
	mode text ,
	tid xid ,
	vtid text ,
	pid integer ,
	blocking_pids integer[] ,
	granted boolean
);

Hakanan, don hanzarta shigarwa, babu fihirisa ko hani.

Don adana tarihin kanta, ana amfani da tebur da aka raba:

aiki_hist.archive_locking:

DROP TABLE IF EXISTS activity_hist.archive_locking;
CREATE TABLE activity_hist.archive_locking
(
	timepoint timestamp without time zone ,
	locktype text ,
	relation oid ,
	mode text ,
	tid xid ,
	vtid text ,
	pid integer ,
	blocking_pids integer[] ,
	granted boolean	
)
PARTITION BY RANGE (timepoint);

Tun da a cikin wannan yanayin babu buƙatun don saurin shigarwa, an ƙirƙiri wasu fihirisa don hanzarta ƙirƙirar rahotanni.

2. Cika tarihin yanzu

Don tattara hotunan gani kai tsaye, ana amfani da rubutun bash wanda ke gudanar da aikin plpgsql.

samun_aikin_yanzu.sh

#!/bin/bash
#########################################################
#get_current_activity.sh

ERROR_FILE='/home/demon/get_current_activity'$(date +%Y%m%d-)'T'$(date +%H)$(date +%M)$(date +%S)
host=$1
s_name=$2
s_pass=$3

psql  -A -t -q -v ON_ERROR_STOP=1 -c "SELECT activity_hist.get_current_activity( '$host' , '$s_name' , '$s_pass' )" >/dev/null 2>$ERROR_FILE

line_count=`cat $ERROR_FILE | wc -l`
if [[ $line_count != '0' ]];
then
    rm -f /home/demon/*.err >/dev/null 2>/dev/null
	cp $ERROR_FILE $ERROR_FILE'.err' >/dev/null 2>/dev/null  
fi
rm $ERROR_FILE >/dev/null 2>/dev/null
exit 0

plpgsql Ayyukan dblink yana samun damar gani a cikin bayanan da aka yi niyya kuma yana shigar da layuka cikin teburin sabis a cikin bayanan sa ido.

samun_aikin_yanzu.sql

CREATE OR REPLACE FUNCTION activity_hist.get_current_activity( current_host text , current_s_name text , current_s_pass text ) RETURNS BOOLEAN AS $$
DECLARE 
  database_rec record;
  dblink_str text ;
BEGIN   

	EXECUTE 'SELECT dblink_connect(''LINK1'',''host='||current_host||' port=5432 dbname=postgres'||
	                                         ' user='||current_s_name||' password='||current_s_pass|| ' '')';



--------------------------------------------------------------------
--GET pg_stat_activity stats
	INSERT INTO activity_hist.history_pg_stat_activity
	(
		SELECT * FROM dblink('LINK1',
			'SELECT 
			now() , 
			datid             , 
			datname           ,
			pid               ,
			usesysid              ,
			usename              ,
			application_name     ,
			client_addr          ,
			client_hostname      ,
			client_port       ,
			backend_start         ,
			xact_start            ,
			query_start           ,
			state_change          ,
			wait_event_type    ,                     
			wait_event         ,                   
			state              ,                  
			backend_xid         ,                 
			backend_xmin        ,                
			query              ,               
			backend_type   			
		FROM pg_stat_activity
		') 
		AS t (
		    timepoint 		  timestamp without time zone ,			
			datid             oid  , 
			datname           name ,
			pid               integer,
			usesysid          oid    ,
			usename           name   ,
			application_name  text   ,
			client_addr       inet   ,
			client_hostname   text   ,
			client_port       integer,
			backend_start     timestamp with time zone ,
			xact_start        timestamp with time zone ,
			query_start       timestamp with time zone ,
			state_change      timestamp with time zone ,
			wait_event_type   text ,                     
			wait_event        text ,                   
			state             text ,                  
			backend_xid       xid  ,                 
			backend_xmin      xid  ,                
			query             text ,               
			backend_type      text 			
		)
	);

---------------------------------------	
--ACTIVITY_HIST.HISTORY_LOCKING	
	INSERT INTO activity_hist.history_locking
	(
		SELECT * FROM dblink('LINK1',
			'SELECT 
			now() , 
			lock.locktype,
			lock.relation,
			lock.mode,
			lock.transactionid as tid,
			lock.virtualtransaction as vtid,
			lock.pid,
			pg_blocking_pids(lock.pid), 
			lock.granted
			FROM 	pg_catalog.pg_locks lock LEFT JOIN pg_catalog.pg_database db ON db.oid = lock.database
			WHERE NOT lock.pid = pg_backend_pid()	
		') 
		AS t (
			timepoint timestamp without time zone ,
			locktype text ,
			relation oid , 
			mode text ,
			tid xid ,
			vtid text ,
			pid integer ,
			blocking_pids integer[] ,
			granted boolean
		)
	);
	PERFORM dblink_disconnect('LINK1');
	
	RETURN TRUE ;
END
$$ LANGUAGE plpgsql;

Don tattara hotunan hoto, ana amfani da sabis na tsarin da rubutun biyu:

pg_current_activity.sabis

# /etc/systemd/system/pg_current_activity.service
[Unit]
Description=Collect history of pg_stat_activity , pg_locks 
Wants=pg_current_activity.timer

[Service]
Type=forking
StartLimitIntervalSec=0
ExecStart=/home/postgres/pgutils/demon/get_current_activity.sh 10.124.70.40 postgres postgres

[Install]
WantedBy=multi-user.target

pg_current_activity.timer

# /etc/systemd/system/pg_current_activity.timer
[Unit]
Description=Run pg_current_activity.sh every 1 second
Requires=pg_current_activity.service

[Timer]
Unit=pg_current_activity.service
OnCalendar=*:*:0/1
AccuracySec=1

[Install]
WantedBy=timers.target

Sanya haƙƙoƙin rubutu:
# chmod 755 pg_current_activity.timer
# chmod 755 pg_current_activity.sabis

Bari mu fara sabis:
# systemctl daemon-sake saukewa
# systemctl fara pg_current_activity.service

Don haka, ana tattara tarihin ra'ayoyi a cikin sigar hoto na biyu zuwa na biyu. Tabbas, idan an bar komai kamar yadda yake, tebur ɗin za su ƙaru da sauri cikin girman kuma ƙari ko žasa aiki mai fa'ida zai zama ba zai yiwu ba.

Wajibi ne don tsara bayanan adana bayanai.

3. Ajiye tarihin

Don adanawa, ana amfani da rumbun adana kayan tarihi*.

Ana ƙirƙira sabbin ɓangarori a kowace sa'a, yayin da aka cire tsoffin bayanai daga tebur * tarihin, don haka girman tebur * ba ya canzawa da yawa kuma saurin shigarwa baya raguwa akan lokaci.

Ƙirƙirar sabbin sassa ana yin ta aikin aikin plpgsql_hist.archive_current_activity. Algorithm na aiki abu ne mai sauqi qwarai (amfani da misalin sashin don tebur_pg_stat_activity).

Ƙirƙiri kuma cika sabon sashe

EXECUTE format(
'CREATE TABLE ' || partition_name || 
' PARTITION OF activity_hist.archive_pg_stat_activity FOR VALUES FROM ( %L ) TO ( %L ) ' , 
to_char(date_trunc('year', partition_min_range ),'YYYY')||'-'||
to_char(date_trunc('month', partition_min_range ),'MM')||'-'||
to_char(date_trunc('day', partition_min_range ),'DD')||' '||
to_char(date_trunc('hour', partition_min_range ),'HH24')||':00', 
to_char(date_trunc('year', partition_max_range ),'YYYY')||'-'||
to_char(date_trunc('month', partition_max_range ),'MM')||'-'||
to_char(date_trunc('day', partition_max_range ),'DD')||' '||
to_char(date_trunc('hour', partition_max_range ),'HH24')||':00'
);

INSERT INTO activity_hist.archive_pg_stat_activity
(
	SELECT 	* 
	FROM 	activity_hist.history_pg_stat_activity
	WHERE 	timepoint BETWEEN partition_min_range AND partition_max_range 		
);

Ƙirƙirar fihirisa

EXECUTE format	(
'CREATE INDEX '||index_name||
' ON '||partition_name||' ( wait_event_type , backend_type , timepoint )' 
);

EXECUTE format	('CREATE INDEX '||index_name||
' ON '||partition_name||' ( wait_event_type , backend_type , timepoint , queryid )' 
);

Cire tsoffin bayanai daga teburin tarihin_pg_stat_activity

DELETE 
FROM 	activity_hist.history_pg_stat_activity
WHERE 	timepoint < partition_max_range;

Tabbas, daga lokaci zuwa lokaci, ana share tsoffin sassan kamar yadda ba dole ba ne.

Rahotanni na asali

A gaskiya, me ya sa ake yin haka? Don samun rahotannin da ba su da tabbas game da Oracle's AWR.

Yana da mahimmanci don ƙara cewa don karɓar rahotanni, kuna buƙatar gina haɗi tsakanin pg_stat_activity da ra'ayoyin pg_stat_statements. Ana haɗe tebur ɗin ta ƙara ginshiƙin 'queryid' zuwa teburin 'history_pg_stat_activity', 'archive_pg_stat_activity'. Hanyar ƙara ƙimar shafi ya wuce iyakar wannan labarin kuma an kwatanta shi a nan - pg_stat_statements + pg_stat_activity + loq_query = pg_ash? .

JAM'IN LOKACIN CPU don TAMBAYOYI

nema:

WITH hist AS
(
SELECT 
	aa.query ,aa.queryid ,			
	count(*) * interval '1 second' AS duration 
FROM 	activity_hist.archive_pg_stat_activity aa
WHERE timepoint BETWEEN pg_stat_history_begin+(current_hour_diff * interval '1 hour') AND  pg_stat_history_end+(current_hour_diff * interval '1 hour')  AND backend_type = 'client backend' AND datname != 'postgres' AND	( aa.wait_event_type IS NULL  ) ANDaa.state = 'active'
GROUP BY aa.wait_event_type , aa.wait_event , aa.query ,aa.queryid		
UNION 
SELECT 
	ha.query ,ha.queryid,
	count(*) * interval '1 second' AS duration 
FROM 	activity_hist.history_pg_stat_activity_for_reports ha
WHERE timepoint BETWEEN pg_stat_history_begin+(current_hour_diff * interval '1 hour') AND pg_stat_history_end+(current_hour_diff * interval '1 hour')  AND 	backend_type = 'client backend' AND datname != 'postgres' AND ( ha.wait_event_type IS NULL  )AND ha.state = 'active'
GROUP BY ha.wait_event_type , ha.wait_event , ha.query ,ha.queryid		
)
SELECT 	query , queryid , SUM( duration ) as duration 
FROM hist
GROUP BY  query , queryid 
ORDER BY 3 DESC

Alal misali:

-------------------------------------------------------------------
| TOTAL CPU TIME FOR QUERIES : 07:47:36
+----+----------------------------------------+--------------------
|   #|                                 queryid|            duration
+----+----------------------------------------+--------------------
|   1|                      389015618226997618|            04:28:58
|   2|                                        |            01:07:29
|   3|                     1237430309438971376|            00:59:38
|   4|                     4710212362688288619|            00:50:48
|   5|                       28942442626229688|            00:15:50
|   6|                     9150846928388977274|            00:04:46
|   7|                    -6572922443698419129|            00:00:06
|   8|                                        |            00:00:01
+----+----------------------------------------+--------------------

JAMA'A LOKACIN JIRAN TAMBAYOYI

nema:

WITH hist AS
(
SELECT 
	aa.query ,aa.queryid ,			
	count(*) * interval '1 second' AS duration 
FROM 	activity_hist.archive_pg_stat_activity aa
WHERE timepoint BETWEEN pg_stat_history_begin+(current_hour_diff * interval '1 hour') AND pg_stat_history_end+(current_hour_diff * interval '1 hour')  AND 
	backend_type = 'client backend' AND datname != 'postgres' AND
	( aa.wait_event_type IS NOT NULL  ) 
GROUP BY aa.wait_event_type , aa.wait_event , aa.query ,aa.queryid		
UNION 
SELECT 
	ha.query ,ha.queryid,
	count(*) * interval '1 second' AS duration 
FROM 	activity_hist.history_pg_stat_activity_for_reports ha
WHERE timepoint BETWEEN pg_stat_history_begin+(current_hour_diff * interval '1 hour') AND pg_stat_history_end+(current_hour_diff * interval '1 hour')  AND 
	backend_type = 'client backend' AND datname != 'postgres' AND				
	( ha.wait_event_type IS NOT NULL  )
GROUP BY ha.wait_event_type , ha.wait_event , ha.query ,ha.queryid		
)
SELECT 	query , queryid , SUM( duration ) as duration 
FROM hist
GROUP BY  query , queryid 
ORDER BY 3 DESC

Misali:

-------------------------------------------------------------------
| TOTAL WAITINGS TIME FOR QUERIES : 21:55:04
+----+----------------------------------------+--------------------
|   #|                                 queryid|            duration
+----+----------------------------------------+--------------------
|   1|                      389015618226997618|            16:19:05
|   2|                                        |            03:47:04
|   3|                     8085340880788646241|            00:40:20
|   4|                     4710212362688288619|            00:13:35
|   5|                     9150846928388977274|            00:12:25
|   6|                       28942442626229688|            00:11:32
|   7|                     1237430309438971376|            00:09:45
|   8|                     2649515222348904837|            00:09:37
|   9|                                        |            00:03:45
|  10|                     3167065002719415275|            00:02:20
|  11|                     5731212217001535134|            00:02:13
|  12|                     8304755792398128062|            00:01:31
|  13|                     2649515222348904837|            00:00:59
|  14|                     2649515222348904837|            00:00:22
|  15|                                        |            00:00:12
|  16|                     3422818749220588372|            00:00:08
|  17|                    -5730801771815999400|            00:00:03
|  18|                    -1473395109729441239|            00:00:02
|  19|                     2404820632950544954|            00:00:02
|  20|                    -6572922443698419129|            00:00:02
|  21|                     2369289265278398647|            00:00:01
|  22|                      180077086776069052|            00:00:01
+----+----------------------------------------+--------------------

JIRAN TAMBAYOYI

Bukatu:

WITH hist AS
(
SELECT 
	aa.wait_event_type , aa.wait_event 
FROM 	activity_hist.archive_pg_stat_activity aa
WHERE timepoint BETWEEN pg_stat_history_begin+(current_hour_diff * interval '1 hour') AND pg_stat_history_end+(current_hour_diff * interval '1 hour') AND 
	backend_type = 'client backend' AND datname != 'postgres' AND
	aa.wait_event IS NOT NULL 
GROUP BY aa.wait_event_type , aa.wait_event
UNION 
SELECT 
	ha.wait_event_type , ha.wait_event 
FROM 	activity_hist.history_pg_stat_activity_for_reports ha
WHERE timepoint BETWEEN pg_stat_history_begin+(current_hour_diff * interval '1 hour') AND pg_stat_history_end+(current_hour_diff * interval '1 hour') AND 
	backend_type = 'client backend' AND datname != 'postgres' AND
	ha.wait_event IS NOT NULL 
GROUP BY ha.wait_event_type , ha.wait_event		
)
SELECT 	wait_event_type , wait_event 
FROM hist
GROUP BY wait_event_type , wait_event
ORDER BY 1 ASC,2 ASC

----------------------------------------------------------------------

WITH hist AS
(
SELECT 
	aa.wait_event_type , aa.wait_event , aa.query ,aa.queryid ,			
	count(*) * interval '1 second' AS duration 
FROM 	activity_hist.archive_pg_stat_activity aa
WHERE timepoint BETWEEN pg_stat_history_begin+(current_hour_diff * interval '1 hour') AND pg_stat_history_end+(current_hour_diff * interval '1 hour') AND 
	backend_type = 'client backend' AND datname != 'postgres' AND
	( aa.wait_event_type = waitings_stat_rec.wait_event_type AND aa.wait_event = waitings_stat_rec.wait_event )
GROUP BY aa.wait_event_type , aa.wait_event , aa.query ,aa.queryid		
UNION 
SELECT 
	ha.wait_event_type , ha.wait_event , ha.query ,ha.queryid,
	count(*) * interval '1 second' AS duration 
FROM 	activity_hist.history_pg_stat_activity_for_reports ha
WHERE timepoint BETWEEN pg_stat_history_begin+(current_hour_diff * interval '1 hour') AND pg_stat_history_end+(current_hour_diff * interval '1 hour') AND 
	backend_type = 'client backend' AND datname != 'postgres' AND				
	( ha.wait_event_type = waitings_stat_rec.wait_event_type AND ha.wait_event = waitings_stat_rec.wait_event )
GROUP BY ha.wait_event_type , ha.wait_event , ha.query ,ha.queryid		
)
SELECT 	query , queryid , SUM( duration ) as duration 
FROM hist
GROUP BY  query , queryid 
ORDER BY 3 DESC

Alal misali:

------------------------------------------------
| WAITINGS FOR QUERIES
+-----------------------------------------------
|                      wait_event_type = Client|
|                       wait_event = ClientRead|
|                        Total time  = 00:46:56|
------------------------------------------------
|    #|             queryid|            duration
+-----+--------------------+--------------------
|    1| 8085340880788646241|            00:40:20
|    2|                    |            00:03:45
|    3| 5731212217001535134|            00:01:53
|    4|                    |            00:00:12
|    5| 9150846928388977274|            00:00:09
|    6| 3422818749220588372|            00:00:08
|    7| 1237430309438971376|            00:00:06
|    8|   28942442626229688|            00:00:05
|    9| 4710212362688288619|            00:00:05
|   10|-5730801771815999400|            00:00:03
|   11| 8304755792398128062|            00:00:02
|   12|-6572922443698419129|            00:00:02
|   13|-1473395109729441239|            00:00:02
|   14| 2404820632950544954|            00:00:02
|   15|  180077086776069052|            00:00:01
|   16| 2369289265278398647|            00:00:01

+-----------------------------------------------
|                          wait_event_type = IO|
|                      wait_event = BufFileRead|
|                        Total time  = 00:00:38|
------------------------------------------------
|    #|             queryid|            duration
+-----+--------------------+--------------------
|    1|   28942442626229688|            00:00:38

+-----------------------------------------------

TARIHIN HANYOYIN KYAUTA

nema:

SELECT 
MIN(date_trunc('second',timepoint)) AS started , 
	count(*) * interval '1 second' as duration ,
	pid , blocking_pids , relation , mode , locktype 	 
FROM 
	activity_hist.archive_locking al 
WHERE 
	timepoint BETWEEN pg_stat_history_begin+(current_hour_diff * interval '1 hour') AND pg_stat_history_end+(current_hour_diff * interval '1 hour') AND
	NOT granted AND 
	locktype = 'relation' 
GROUP BY pid , blocking_pids , relation , mode , locktype			
UNION
SELECT 
	MIN(date_trunc('second',timepoint)) AS started , 
	count(*) * interval '1 second' as duration ,
	pid , blocking_pids , relation , mode , locktype
FROM 
	activity_hist.history_locking 
WHERE 
	timepoint BETWEEN pg_stat_history_begin+(current_hour_diff * interval '1 hour') AND pg_stat_history_end+(current_hour_diff * interval '1 hour') AND
	NOT granted AND 
	locktype = 'relation' 
GROUP BY pid , blocking_pids , relation , mode , locktype			
ORDER BY 1

Alal misali:

------------------------------------------------- ------------------------------------------------- --------------------------------- | KULLE TARIHIN HANYOYI +------------- -------------------------------- +------------------ | #| pid | fara| tsawon lokaci| blocking_pids| dangantaka| yanayin| nau'in kulle-kulle -------------------------------------- ------------------------------------- ------------- | 1| 26224| 2019-09-02 19:32:16| 00:01:45| {26211}| 16541| AccessShareLock| dangantaka | 2| 26390| 2019-09-02 19:34:03| 00:00:53| {26211}| 16541| AccessShareLock| dangantaka | 3| 26391| 2019-09-02 19:34:03| 00:00:53| {26211}| 16541| AccessShareLock| dangantaka | 4| 26531| 2019-09-02 19:35:27| 00:00:12| {26211}| 16541| AccessShareLock| dangantaka | 5| 27284| 2019-09-02 19:44:02| 00:00:19| {27276}| 16541| AccessShareLock| dangantaka | 6| 27283| 2019-09-02 19:44:02| 00:00:19| {27276}| 16541| AccessShareLock| dangantaka | 7| 27286| 2019-09-02 19:44:02| 00:00:19| {27276}| 16541| AccessShareLock| dangantaka | 8| 27423| 2019-09-02 19:45:24| 00:00:12| {27394}| 16541| AccessShareLock| dangantaka | 9| 27648| 2019-09-02 19:48:06| 00:00:20| {27647}| 16541| AccessShareLock| dangantaka | 10| 27650| 2019-09-02 19:48:06| 00:00:20| {27647}| 16541| AccessShareLock| dangantaka | 11| 27735| 2019-09-02 19:49:08| 00:00:06| {27650}| 16541| AccessExclusiveLock| dangantaka | 12| 28380| 2019-09-02 19:56:03| 00:01:56| {28379}| 16541| AccessShareLock| dangantaka | 13| 28379| 2019-09-02 19:56:03| 00:00:01| 28377| 16541| AccessExclusiveLock| dangantaka | | | | | 28376| |

TARIHIN HANYOYIN KASHE TARIHIN

Bukatu:

SELECT 
blocking_pids 
FROM 
	activity_hist.archive_locking al 
WHERE 
	timepoint BETWEEN pg_stat_history_begin+(current_hour_diff * interval '1 hour') AND pg_stat_history_end+(current_hour_diff * interval '1 hour') AND
	NOT granted AND 
	locktype = 'relation' 
GROUP BY blocking_pids 		
UNION
SELECT 
	blocking_pids 
FROM 
	activity_hist.history_locking 
WHERE 
	timepoint BETWEEN pg_stat_history_begin+(current_hour_diff * interval '1 hour') AND pg_stat_history_end+(current_hour_diff * interval '1 hour') AND
	NOT granted AND 
	locktype = 'relation' 
GROUP BY blocking_pids 		
ORDER BY 1

---------------------------------------------------------------

SELECT 
	pid , usename , application_name , datname ,
	MIN(date_trunc('second',timepoint)) as started , 
	count(*) * interval '1 second' as duration ,		 
	state , 
	query
				FROM  	activity_hist.archive_pg_stat_activity
				WHERE 	pid= current_pid AND 
						timepoint BETWEEN pg_stat_history_begin+(current_hour_diff * interval '1 hour') AND pg_stat_history_end+(current_hour_diff * interval '1 hour') 						 
				GROUP BY pid , usename , application_name , 
						datname , 
						state_change, 
						state , 
						query 
				UNION
				SELECT 
					pid , usename , application_name , datname ,
					MIN(date_trunc('second',timepoint)) as started , 
					count(*) * interval '1 second' as duration ,		 
					state , 
					query
				FROM  	activity_hist.history_pg_stat_activity_for_reports
				WHERE 	pid= current_pid AND 
						timepoint BETWEEN pg_stat_history_begin+(current_hour_diff * interval '1 hour') AND pg_stat_history_end+(current_hour_diff * interval '1 hour') 						 
				GROUP BY pid , usename , application_name , 
						datname , 
						state_change, 
						state , 
						query 
				ORDER BY 5 , 1

Alal misali:

------------------------------------------------- ------------------------------------------------- ------------------------------------------------- ------------------------------ ----------------------- ------------------- --------------------------------------------------------- | #| pid | sunan amfani| application_name| datname| fara| tsawon lokaci| jiha| tambaya +---------------------------- --------------------- ------------------------------------------------------------------ ----------------- | 1| 26211| tusar| psql| tdb1| 2019-09-02 19:31:54| 00:00:04| aiki | | 2| 26211| tusar| psql| tdb1| 2019-09-02 19:31:58| 00:00:06| banza a cikin ciniki| fara; | 3| 26211| tusar| psql| tdb1| 2019-09-02 19:32:16| 00:01:45| banza a cikin ciniki| kulle tebur wafer_data; | 4| 26211| tusar| psql| tdb1| 2019-09-02 19:35:54| 00:01:23| aiki | aikata; | 5| 26211| tusar| psql| tdb1| 2019-09-02 19:38:46| 00:00:02| banza a cikin ciniki| fara; | 6| 26211| tusar| psql| tdb1| 2019-09-02 19:38:54| 00:00:08| banza a cikin ciniki| kulle tebur wafer_data; | 7| 26211| tusar| psql| tdb1| 2019-09-02 19:39:08| 00:42:42| aiki | aikata; | 8| 26211| tusar| psql| tdb1| 2019-09-03 07:12:07| 00:00:52| aiki| zaɓi test_del ();

Ci gaba.

Tambayoyi na asali da aka nuna da rahotannin da aka samu sun riga sun sauƙaƙa rayuwa yayin nazarin abubuwan da suka faru.
Dangane da ainihin tambayoyin, zaku iya samun rahoton da yayi kama da Oracle's AWR.
Misalin rahoton taƙaitawa

------------------------------------------------ ---------------------------------- | HADAKAR RAHOTANNI NA AIKI DA JIRA.

A ci gaba. Na gaba a layi shine ƙirƙirar tarihin kulle (pg_stat_locks), ƙarin cikakken bayanin tsarin cike tebur.

source: www.habr.com

Add a comment