ProHoster > blog > administrasi > Upaya untuk membuat analog ASH untuk PostgreSQL

Upaya untuk membuat analog ASH untuk PostgreSQL

Pernyataan masalah

Untuk mengoptimalkan kueri PostgreSQL, kemampuan menganalisis riwayat aktivitas, khususnya menunggu, mengunci, dan statistik tabel, sangat diperlukan.

Peluang yang tersedia

Alat Analisis Beban Kerja Historis atau "AWR untuk Postgres": solusi yang sangat menarik, tetapi tidak ada riwayat pg_stat_activity dan pg_locks.

ekstensi halaman :
«Semua informasi yang terakumulasi hanya disimpan dalam RAM, dan jumlah memori yang dikonsumsi diatur oleh jumlah catatan yang terakhir disimpan.

Bidang queryid ditambahkan - queryid yang sama dari ekstensi pg_stat_statements (diperlukan pra-instalasi).«

Ini tentu saja akan sangat membantu, tapi hal yang paling menyusahkan adalah poin pertama.”Semua informasi yang terakumulasi hanya disimpan dalam RAM ”, yaitu ada dampak pada basis target. Selain itu, tidak ada riwayat kunci dan statistik tabel. Itu. solusinya secara umum tidak lengkap: “Belum ada paket siap pakai untuk instalasi. Disarankan untuk mengunduh sumber dan merakit sendiri perpustakaannya. Pertama-tama Anda perlu menginstal paket “devel” untuk server Anda dan mengatur jalur ke pg_config di variabel PATH.".

Secara umum, ada banyak keributan, dan dalam kasus database produksi yang serius, server mungkin tidak dapat melakukan apa pun. Kita perlu menemukan sesuatu milik kita sendiri lagi.

Peringatan

Karena volumenya yang agak besar dan karena periode pengujian yang tidak lengkap, artikel ini sebagian besar bersifat informasional, melainkan sebagai kumpulan tesis dan hasil antara.
Materi yang lebih detail akan disiapkan nanti, sebagian

Draf persyaratan untuk solusinya

Penting untuk mengembangkan alat yang memungkinkan Anda menyimpan:

pg_stat_activity melihat riwayat
Riwayat kunci sesi menggunakan tampilan pg_locks

Persyaratan solusi–meminimalkan dampak pada database target.

Ide umum– agen pengumpulan data diluncurkan bukan di database target, tetapi di database pemantauan sebagai layanan systemd. Ya, beberapa kehilangan data mungkin terjadi, namun hal ini tidak penting untuk pelaporan, namun tidak ada dampak pada database target dalam hal memori dan ruang disk. Dan jika menggunakan kumpulan koneksi, dampaknya terhadap proses pengguna minimal.

Tahapan implementasi

1. Meja layanan

Skema tersendiri digunakan untuk menyimpan tabel, agar tidak mempersulit analisis tabel utama yang digunakan.

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

Penting: Skema tidak dibuat di database target, namun di database pemantauan.

pg_stat_activity melihat riwayat

Tabel digunakan untuk menyimpan snapshot terkini dari tampilan pg_stat_activity

aktivitas_hist.history_pg_stat_aktivitas :

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

Untuk mempercepat penyisipan - tidak ada indeks atau batasan.

Untuk menyimpan riwayat itu sendiri, tabel yang dipartisi digunakan:

aktivitas_hist.archive_pg_stat_aktivitas :

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

Karena dalam hal ini tidak ada persyaratan kecepatan penyisipan, beberapa indeks telah dibuat untuk mempercepat pembuatan laporan.

Riwayat pemblokiran sesi

Sebuah tabel digunakan untuk menyimpan snapshot kunci sesi saat ini:

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

Selain itu, untuk mempercepat penyisipan, tidak ada indeks atau batasan.

Untuk menyimpan riwayat itu sendiri, tabel yang dipartisi digunakan:

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

Karena dalam hal ini tidak ada persyaratan kecepatan penyisipan, beberapa indeks telah dibuat untuk mempercepat pembuatan laporan.

2.Mengisi riwayat saat ini

Untuk mengumpulkan cuplikan tampilan secara langsung, skrip bash digunakan yang menjalankan fungsi plpgsql.

dapatkan_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

tolong Fungsi dblink mengakses tampilan di database target dan menyisipkan baris ke dalam tabel layanan di database pemantauan.

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;

Untuk mengumpulkan cuplikan tampilan, layanan systemd dan dua skrip digunakan:

pg_current_activity.layanan

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

Tetapkan hak untuk skrip:
# chmod 755 pg_current_activity.timer
# chmod 755 pg_current_activity.service

Mari kita mulai layanannya:
# systemctl daemon-ulang
# systemctl mulai pg_current_activity.service

Dengan demikian, sejarah penayangan dikumpulkan dalam bentuk cuplikan detik demi detik. Tentu saja, jika semuanya dibiarkan apa adanya, ukuran tabel akan bertambah dengan sangat cepat dan pekerjaan yang kurang lebih produktif menjadi tidak mungkin.

Penting untuk mengatur pengarsipan data.

3. Riwayat pengarsipan

Untuk pengarsipan, arsip tabel yang dipartisi* digunakan.

Partisi baru dibuat setiap jam, sementara data lama dihapus dari tabel histori*, sehingga ukuran tabel histori* tidak banyak berubah dan kecepatan penyisipan tidak menurun seiring waktu.

Pembuatan bagian baru dilakukan oleh fungsi plpgsql aktivitas_hist.archive_current_activity. Algoritma kerjanya sangat sederhana (menggunakan contoh bagian tabel archive_pg_stat_activity).

Buat dan isi bagian baru

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

Membuat indeks

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

Menghapus data lama dari tabel history_pg_stat_activity

DELETE 
FROM 	activity_hist.history_pg_stat_activity
WHERE 	timepoint < partition_max_range;

Tentu saja, dari waktu ke waktu, bagian lama dihapus karena tidak diperlukan.

Laporan dasar

Sebenarnya kenapa semua ini dilakukan? Untuk mendapatkan laporan yang sangat samar-samar mengingatkan kita pada AWR Oracle.

Penting untuk ditambahkan bahwa untuk menerima laporan, Anda perlu membuat koneksi antara tampilan pg_stat_activity dan pg_stat_statements. Tabel ditautkan dengan menambahkan kolom 'queryid' ke tabel 'history_pg_stat_activity', 'archive_pg_stat_activity'. Metode penambahan nilai kolom berada di luar cakupan artikel ini dan dijelaskan di sini − pg_stat_statements + pg_stat_activity + loq_query = pg_ash? .

TOTAL WAKTU CPU UNTUK KUERI

Meminta :

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

Contoh:

-------------------------------------------------------------------
| 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 WAKTU TUNGGU UNTUK QUERIES

Meminta :

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

Contoh:

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

MENUNGGU PERTANYAAN

Permintaan:

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

Contoh:

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

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

RIWAYAT PROSES TERKUNCI

Minta:

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

Contoh:

--------------------------------------------------- --------------------------------------------------- --------------------------------- | RIWAYAT PROSES TERKUNCI +-----+----------+-----+-------- --+------------ --------+-----+----- --------------- +------------------- | #| pid| dimulai| durasi| memblokir_pids| hubungan| modus| tipe kunci +----------+----------+-----+---------- +--------- -----------+-----------+------- -------------+----- -------------- | 1| 26224| 2019-09-02 19:32:16| 00:01:45| {26211}| 16541| AksesShareLock| hubungan | 2| 26390| 2019-09-02 19:34:03| 00:00:53| {26211}| 16541| AksesShareLock| hubungan | 3| 26391| 2019-09-02 19:34:03| 00:00:53| {26211}| 16541| AksesShareLock| hubungan | 4| 26531| 2019-09-02 19:35:27| 00:00:12| {26211}| 16541| AksesShareLock| hubungan | 5| 27284| 2019-09-02 19:44:02| 00:00:19| {27276}| 16541| AksesShareLock| hubungan | 6| 27283| 2019-09-02 19:44:02| 00:00:19| {27276}| 16541| AksesShareLock| hubungan | 7| 27286| 2019-09-02 19:44:02| 00:00:19| {27276}| 16541| AksesShareLock| hubungan | 8| 27423| 2019-09-02 19:45:24| 00:00:12| {27394}| 16541| AksesShareLock| hubungan | 9| 27648| 2019-09-02 19:48:06| 00:00:20| {27647}| 16541| AksesShareLock| hubungan | 10| 27650| 2019-09-02 19:48:06| 00:00:20| {27647}| 16541| AksesShareLock| hubungan | 11| 27735| 2019-09-02 19:49:08| 00:00:06| {27650}| 16541| AksesKunci Eksklusif| hubungan | 12| 28380| 2019-09-02 19:56:03| 00:01:56| {28379}| 16541| AksesShareLock| hubungan | 13| 28379| 2019-09-02 19:56:03| 00:00:01| 28377| 16541| AksesKunci Eksklusif| hubungan | | | | | 28376| |

RIWAYAT PROSES PEMBLOKIRAN

Permintaan:

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

Contoh:

--------------------------------------------------- --------------------------------------------------- --------------------------------------------------- ----------------------- RIWAYAT PROSES PEMBLOKIRAN +----+----------+------- ---+-----+----------+-------------- ---------------------+-----+--------------------- - ----------------------+------------------------ | #| pid| nama pengguna| nama_aplikasi| nama data| dimulai| durasi| negara bagian| pertanyaan +----------+----------+----------+-----+ --------- -+-----+-----+------ --------------------------+---------------- ------- ----------------- | 1| 26211| pengguna| psql| tdb1| 2019-09-02 19:31:54| 00:00:04| menganggur| | 2| 26211| pengguna| psql| tdb1| 2019-09-02 19:31:58| 00:00:06| menganggur dalam transaksi| mulai; | 3| 26211| pengguna| psql| tdb1| 2019-09-02 19:32:16| 00:01:45| menganggur dalam transaksi| kunci tabel wafer_data; | 4| 26211| pengguna| psql| tdb1| 2019-09-02 19:35:54| 00:01:23| menganggur| melakukan; | 5| 26211| pengguna| psql| tdb1| 2019-09-02 19:38:46| 00:00:02| menganggur dalam transaksi| mulai; | 6| 26211| pengguna| psql| tdb1| 2019-09-02 19:38:54| 00:00:08| menganggur dalam transaksi| kunci tabel wafer_data; | 7| 26211| pengguna| psql| tdb1| 2019-09-02 19:39:08| 00:42:42| menganggur| melakukan; | 8| 26211| pengguna| psql| tdb1| 2019-09-03 07:12:07| 00:00:52| aktif| pilih tes_del();

Perkembangan.

Kueri dasar yang ditampilkan dan laporan yang dihasilkan telah membuat hidup lebih mudah saat menganalisis insiden kinerja.
Berdasarkan pertanyaan dasar, Anda bisa mendapatkan laporan yang agak mirip dengan AWR Oracle.
Contoh laporan ringkasan

+------------------------------------------------- ----------------------------------- | LAPORAN KONSOLIDASIAN UNTUK KEGIATAN DAN TUNGGU.

Bersambung. Baris berikutnya adalah pembuatan riwayat kunci (pg_stat_locks), penjelasan lebih rinci tentang proses pengisian tabel.

Sumber: www.habr.com

Tambah komentar