ProHoster > Blog > Bestjoer > In besykjen om in ASH-analooch te meitsjen foar PostgreSQL

In besykjen om in ASH-analooch te meitsjen foar PostgreSQL

Probleemintwurding

Om PostgreSQL-fragen te optimalisearjen, is de mooglikheid om aktiviteitshistoarje te analysearjen, yn 't bysûnder, wachtsjen, slûzen en tabelstatistiken, heul fereaske.

Beskikbere mooglikheden

Histoarysk ark foar analyse fan wurkdruk as "AWR foar Postgres": in tige nijsgjirrige oplossing, mar der is gjin skiednis fan pg_stat_activity en pg_locks.

pgsentinel extension :
«Alle opboude ynformaasje wurdt opslein allinnich yn RAM, en it bedrach fan ûnthâld ferbrûkt wurdt regele troch it oantal lêste opslein records.

It queryid-fjild wurdt tafoege - deselde queryid fan 'e pg_stat_statements-útwreiding (foarynstallaasje fereaske).«

Dit soe fansels in protte helpe, mar it lestichste is it earste punt."Alle sammele ynformaasje wurdt opslein allinnich yn RAM ”, d.w.s. der is in ynfloed op de doelbasis. Dêrneist is der gjin slot skiednis en tabel statistiken. Dy. de oplossing is oer it algemien net kompleet: "D'r is noch gjin klearmakke pakket foar ynstallaasje. It wurdt suggerearre om de boarnen te downloaden en de bibleteek sels te sammeljen. Jo moatte earst it pakket "ûntwikkelje" foar jo tsjinner ynstallearje en it paad ynstelle nei pg_config yn 'e PATH-fariabele.".

Yn 't algemien is d'r in soad drokte, en yn' t gefal fan serieuze produksjedatabases kin it net mooglik wêze om neat te dwaan mei de tsjinner. Wy moatte wer wat fan ús betinke.

Warskôging.

Troch it frij grutte folume en troch de ûnfolsleine testperioade is it artikel benammen fan ynformative aard, earder as in set fan proefskriften en tuskenresultaten.
Mear detaillearre materiaal sil letter wurde taret, yn dielen

Untwerp easken foar de oplossing

It is needsaaklik om in ark te ûntwikkeljen wêrmei jo kinne opslaan:

pg_stat_activity besjen skiednis
Sesje slot skiednis mei help fan de pg_locks werjefte

Oplossing eask- minimalisearje de ynfloed op 'e doeldatabase.

Algemiene idee- de agint foar it sammeljen fan gegevens wurdt net lansearre yn 'e doeldatabase, mar yn' e tafersjochdatabase as in systemd tsjinst. Ja, wat gegevens ferlies is mooglik, mar dit is net kritysk foar rapportaazje, mar der is gjin ynfloed op de doeldatabase yn termen fan ûnthâld en skiif romte. En yn it gefal fan it brûken fan in ferbiningspool is de ynfloed op brûkersprosessen minimaal.

Implementaasje stadia

1.Tsjinsttafels

In apart skema wurdt brûkt om tabellen te bewarjen, sadat de analyze fan 'e brûkte haadtabellen net komplisearje.

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

Wichtich: It skema wurdt net oanmakke yn de doeldatabase, mar yn de tafersjochdatabase.

pg_stat_activity besjen skiednis

In tabel wurdt brûkt om aktuele snapshots fan 'e werjefte pg_stat_activity op te slaan

activity_hist.history_pg_stat_activity:

--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
);

Om ynfoegje te rapperjen - gjin yndeksen of beheiningen.

Om de skiednis sels op te slaan, wurdt in ferdielde tabel brûkt:

activity_hist.archive_pg_stat_activity:

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);

Om't d'r yn dit gefal gjin easken binne foar ynfoegje snelheid, binne guon yndeksen makke om it meitsjen fan rapporten te rapperjen.

Sesje blokkearjende skiednis

In tabel wurdt brûkt om aktuele snapshots fan sesje-slûzen op te slaan:

activity_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
);

Ek, om ynfoegje te rapperjen, binne d'r gjin yndeksen of beheiningen.

Om de skiednis sels op te slaan, wurdt in ferdielde tabel brûkt:

activity_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);

Om't d'r yn dit gefal gjin easken binne foar ynfoegje snelheid, binne guon yndeksen makke om it meitsjen fan rapporten te rapperjen.

2.De aktuele skiednis ynfolje

Om direkt snapshots te sammeljen, wurdt in bash-skript brûkt dat de plpgsql-funksje útfiert.

get_current_activity.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 De dblink-funksje makket tagong ta werjeften yn 'e doeldatabase en foeget rigen yn yn tsjinsttabellen yn' e tafersjochdatabase.

get_current_activity.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;

Om snapshots te sammeljen, wurde de systemd-tsjinst en twa skripts brûkt:

pg_current_activity.service

# /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

Rjochten tawize oan skripts:
# chmod 755 pg_current_activity.timer
# chmod 755 pg_current_activity.service

Litte wy de tsjinst begjinne:
# systemctl daemon-reload
# systemctl start pg_current_activity.service

Sa wurdt de skiednis fan werjeften sammele yn 'e foarm fan sekonde-by-sekonde snapshots. Fansels, as alles bliuwt sa't it is, sille de tabellen heul gau yn grutte tanimme en mear of minder produktyf wurk sil ûnmooglik wurde.

It is needsaaklik om it argivearjen fan gegevens te organisearjen.

3. Argivearjen skiednis

Foar argivearjen wurde partitionearre tabellen argyf * brûkt.

Nije partysjes wurde elk oere oanmakke, wylst âlde gegevens út 'e histoarje*-tabellen fuortsmiten wurde, sadat de grutte fan 'e histoarje*-tabellen net folle feroaret en de ynfoegjesnelheid yn 'e rin fan' e tiid net degradearret.

It oanmeitsjen fan nije seksjes wurdt útfierd troch de plpgsql-funksje activity_hist.archive_current_activity. It algoritme fan wurk is heul ienfâldich (mei it foarbyld fan 'e seksje foar de tabel archive_pg_stat_activity).

Meitsje en folje in nije seksje yn

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 		
);

It meitsjen fan yndeksen

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 )' 
);

It fuortsmiten fan âlde gegevens út de history_pg_stat_activity tabel

DELETE 
FROM 	activity_hist.history_pg_stat_activity
WHERE 	timepoint < partition_max_range;

Fansels, fan tiid ta tiid, âlde seksjes wurde wiske as net nedich.

Basis rapporten

Eigentlik, wêrom wurdt dit alles dien? Om rapporten te krijen dy't heul vague docht tinken oan Oracle's AWR.

It is wichtich om ta te foegjen dat om rapporten te ûntfangen, jo in ferbining moatte bouwe tusken de werjeften pg_stat_activity en pg_stat_statements. De tabellen wurde keppele troch in kolom 'queryid' ta te foegjen oan 'e tabellen 'history_pg_stat_activity', 'archive_pg_stat_activity'. De metoade foar it tafoegjen fan in kolomwearde is bûten it berik fan dit artikel en wurdt hjir beskreaun - pg_stat_statements + pg_stat_activity + loq_query = pg_ash? .

TOTAL CPU TIID FOAR QUERIES

Fersyk:

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

Foarbyld:

-------------------------------------------------------------------
| 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
+----+----------------------------------------+--------------------

TOTAL WAITINGS TIID FOAR QUERIES

Fersyk:

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

Foarbyld:

-------------------------------------------------------------------
| 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
+----+----------------------------------------+--------------------

WACHTEN OP QUERIES

Fersiken:

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

Foarbyld:

------------------------------------------------
| 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

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

SLOTTE PROSESSEN HISTORY

Fersyk:

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

Foarbyld:

-------------------------------------------------- -------------------------------------------------- ---------------------------------- | SLOTTE PROSESSEN HISTORY +-----+----------------+-------- --+------------ --------+---------------------+----------------------------- +------------------------ | #| pid| begûn| doer| blocking_pids| relaasje| modus| slottype +--------------------------------- -----------------------------------------+----- -------------- | 1| 26224| 2019-09-02 19:32:16| 00:01:45| {26211}| 16541| AccessShareLock| relaasje | 2| 26390| 2019-09-02 19:34:03| 00:00:53| {26211}| 16541| AccessShareLock| relaasje | 3| 26391| 2019-09-02 19:34:03| 00:00:53| {26211}| 16541| AccessShareLock| relaasje | 4| 26531| 2019-09-02 19:35:27| 00:00:12| {26211}| 16541| AccessShareLock| relaasje | 5| 27284| 2019-09-02 19:44:02| 00:00:19| {27276}| 16541| AccessShareLock| relaasje | 6| 27283| 2019-09-02 19:44:02| 00:00:19| {27276}| 16541| AccessShareLock| relaasje | 7| 27286| 2019-09-02 19:44:02| 00:00:19| {27276}| 16541| AccessShareLock| relaasje | 8| 27423| 2019-09-02 19:45:24| 00:00:12| {27394}| 16541| AccessShareLock| relaasje | 9| 27648| 2019-09-02 19:48:06| 00:00:20| {27647}| 16541| AccessShareLock| relaasje | 10| 27650| 2019-09-02 19:48:06| 00:00:20| {27647}| 16541| AccessShareLock| relaasje | 11| 27735| 2019-09-02 19:49:08| 00:00:06| {27650}| 16541| AccessExclusiveLock| relaasje | 12| 28380| 2019-09-02 19:56:03| 00:01:56| {28379}| 16541| AccessShareLock| relaasje | 13| 28379| 2019-09-02 19:56:03| 00:00:01| 28377| 16541| AccessExclusiveLock| relaasje | | | | | 28376| |

BLOKKERING PROSESSEN HISTORY

Fersiken:

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

Foarbyld:

-------------------------------------------------- -------------------------------------------------- -------------------------------------------------- ----------------------- HISTORY BLOKKERING PROSESSEN +----+------------ ---+--------------------+---------------- ------+----------------------------+------- -------+----------------------------------------------- | #| pyk| gebrûksnamme| applikaasje_namme| datname| begûn| doer| steat| query +--------------------------------- --+--------------------+------------------------ --+------ --------------------------+---------------- ------- ------------------ | 1| 26211| tusker| psql| tdb1| 2019-09-02 19:31:54| 00:00:04| idel| | 2| 26211| tusker| psql| tdb1| 2019-09-02 19:31:58| 00:00:06| idle yn transaksje| begjinne; | 3| 26211| tusker| psql| tdb1| 2019-09-02 19:32:16| 00:01:45| idle yn transaksje| slot tafel wafer_data; | 4| 26211| tusker| psql| tdb1| 2019-09-02 19:35:54| 00:01:23| idel| bedriuwe; | 5| 26211| tusker| psql| tdb1| 2019-09-02 19:38:46| 00:00:02| idle yn transaksje| begjinne; | 6| 26211| tusker| psql| tdb1| 2019-09-02 19:38:54| 00:00:08| idle yn transaksje| slot tafel wafer_data; | 7| 26211| tusker| psql| tdb1| 2019-09-02 19:39:08| 00:42:42| idel| bedriuwe; | 8| 26211| tusker| psql| tdb1| 2019-09-03 07:12:07| 00:00:52| aktyf| selektearje test_del();

Ûntwikkeling.

De werjûn basisfragen en de resultearjende rapporten meitsje it libben al folle makliker by it analysearjen fan prestaasjesynsidinten.
Op grûn fan basisfragen kinne jo in rapport krije dat vague liket op Oracle's AWR.
Gearfetting rapport foarbyld

+------------------------------------------------ ---------------------------------- | KONSOLIDEERDE RAPPORT FOAR AKTIVITEIT EN WAITINGS.

Wurdt ferfolge. Folgjende yn line is it meitsjen fan in slot skiednis (pg_stat_locks), in mear detaillearre beskriuwing fan it proses fan it ynfoljen fan tabellen.

Boarne: www.habr.com

Add a comment