pgsentinel واڌارو :
«سموري جمع ڪيل معلومات صرف رام ۾ محفوظ ڪئي وئي آهي، ۽ ميموري جي استعمال ڪيل رقم آخري ذخيرو رڪارڊ جي تعداد جي ذريعي منظم ڪئي وئي آهي.
اهو، يقينا، تمام گهڻو مدد ڪندو، پر سڀ کان وڌيڪ ڏکوئيندڙ شيء پهريون نقطو آهي.سموري معلومات صرف رام ۾ محفوظ ٿيل آهي ”، يعني ھدف جي بنياد تي ھڪڙو اثر آھي. ان کان علاوه، ڪو به تالا تاريخ ۽ ٽيبل جي انگ اکر نه آهي. اهي. حل عام طور تي ناممڪن آهي: "انسٽاليشن لاءِ اڃا تائين ڪو به تيار ٿيل پيڪيج ناهي. اهو تجويز ڪيل آهي ته ذريعن کي ڊائون لوڊ ڪريو ۽ لائبريري پاڻ کي گڏ ڪريو. توهان کي پهريان توهان جي سرور لاءِ “devel” پيڪيج انسٽال ڪرڻ جي ضرورت آهي ۽ PATH متغير ۾ pg_config ڏانهن رستو مقرر ڪريو.".
عام طور تي، اتي تمام گهڻو پريشان آهي، ۽ سنجيده پيداوار ڊيٽابيس جي صورت ۾، اهو سرور سان ڪجهه ڪرڻ ممڪن ناهي. اسان کي ٻيهر پنهنجي پاڻ سان گڏ اچڻ جي ضرورت آهي.
ڊيڄاريندڙ.
بلڪه وڏي مقدار جي ڪري ۽ نامڪمل جاچ واري دور جي ڪري، مضمون بنيادي طور تي معلوماتي نوعيت جو آهي، بلڪه ٿيسز ۽ وچولي نتيجن جي هڪ سيٽ جي طور تي.
وڌيڪ تفصيلي مواد بعد ۾ تيار ڪيو ويندو، حصن ۾
حل جي ضرورتن جو مسودو
اهو ضروري آهي ته هڪ اوزار ٺاهيو جيڪو توهان کي ذخيرو ڪرڻ جي اجازت ڏئي ٿو:
pg_stat_activity ڏسڻ جي تاريخ سيشن تالا جي تاريخ استعمال ڪندي pg_locks ڏيک
حل جي گهرج- ٽارگيٽ ڊيٽابيس تي اثر گھٽايو.
عام خيال- ڊيٽا گڏ ڪرڻ وارو ايجنٽ ٽارگيٽ ڊيٽابيس ۾ نه، پر مانيٽرنگ ڊيٽابيس ۾ هڪ سسٽم سروس جي طور تي شروع ڪيو ويو آهي. ها، ڪجهه ڊيٽا نقصان ممڪن آهي، پر اهو رپورٽنگ لاء اهم ناهي، پر ميموري ۽ ڊسڪ اسپيس جي لحاظ کان ٽارگيٽ ڊيٽابيس تي ڪو به اثر نه آهي. ۽ ڪنيڪشن پول استعمال ڪرڻ جي صورت ۾، صارف جي عمل تي اثر گهٽ ۾ گهٽ آهي.
لاڳو ڪرڻ جا مرحلا
1.Service ٽيبل
جدولن کي ذخيرو ڪرڻ لاءِ هڪ الڳ اسڪيما استعمال ڪيو ويندو آهي، جيئن استعمال ٿيل مکيه جدولن جي تجزيي کي پيچيده نه ڪجي.
DROP SCHEMA IF EXISTS activity_hist ;
CREATE SCHEMA activity_hist AUTHORIZATION monitor ;
اھم: اسڪيما ھدف واري ڊيٽابيس ۾ پيدا نه ڪئي وئي آھي، پر مانيٽرنگ ڊيٽابيس ۾.
pg_stat_activity ڏسڻ جي تاريخ
pg_stat_activity view جي موجوده تصويرن کي ذخيرو ڪرڻ لاءِ ٽيبل استعمال ڪيو ويندو آهي
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
);
داخل ڪرڻ کي تيز ڪرڻ لاءِ - ڪا به انڊيڪس يا پابنديون.
تاريخ پاڻ کي ذخيرو ڪرڻ لاء، هڪ ورهاڱي واري ٽيبل استعمال ڪيو ويندو آهي:
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);
جيئن ته هن معاملي ۾ داخل ڪرڻ جي رفتار لاء ڪا ضرورت ناهي، ڪجهه انڊيڪس ٺاهيا ويا آهن رپورٽون ٺاهڻ جي رفتار کي تيز ڪرڻ لاء.
سيشن بلاڪ ڪرڻ جي تاريخ
سيشن لاڪ جي موجوده تصويرن کي ذخيرو ڪرڻ لاءِ ٽيبل استعمال ڪيو ويندو آهي:
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
);
انهي سان گڏ، اندراج کي تيز ڪرڻ لاء، ڪو به انڊيڪس يا پابنديون نه آهن.
تاريخ پاڻ کي ذخيرو ڪرڻ لاء، هڪ ورهاڱي واري ٽيبل استعمال ڪيو ويندو آهي:
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);
جيئن ته هن معاملي ۾ داخل ڪرڻ جي رفتار لاء ڪا ضرورت ناهي، ڪجهه انڊيڪس ٺاهيا ويا آهن رپورٽون ٺاهڻ جي رفتار کي تيز ڪرڻ لاء.
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;
ڏسڻ جي تصويرن کي گڏ ڪرڻ لاء، سسٽم ڊي سروس ۽ ٻه اسڪرپٽ استعمال ڪيا ويا آهن:
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
لکت جا حق مقرر ڪريو:
# chmod 755 pg_current_activity.timer
# chmod 755 pg_current_activity.service
نيون ورهاڱي هر ڪلاڪ ٺاهيا ويندا آهن، جڏهن ته پراڻي ڊيٽا کي هٽايو ويندو آهي تاريخ * جدولن مان، تنهنڪري تاريخ * جدولن جو سائز گهڻو تبديل نه ٿيندو آهي ۽ وقت سان گڏ داخل ڪرڻ جي رفتار خراب نه ٿيندي آهي.
نون حصن جي تخليق plpgsql فنڪشن جي ذريعي ڪئي وئي آهي activity_hist.archive_current_activity. ڪم جو الگورتھم بلڪل سادو آھي (آرڪائيو_pg_stat_activity ٽيبل لاءِ سيڪشن جو مثال استعمال ڪندي).
نئون سيڪشن ٺاهيو ۽ ڀريو
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
);
انڊيڪس ٺاهڻ
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 )'
);
تاريخ_pg_stat_activity ٽيبل مان پراڻي ڊيٽا کي هٽائڻ
DELETE
FROM activity_hist.history_pg_stat_activity
WHERE timepoint < partition_max_range;
يقينن، وقت بوقت، پراڻن حصن کي غير ضروري طور ختم ڪيو وڃي ٿو.
بنيادي رپورٽون
دراصل اهو سڀ ڪجهه ڇو ڪيو پيو وڃي؟ رپورٽون حاصل ڪرڻ لاءِ تمام مبہم طور تي Oracle's AWR جي ياد ڏياريندڙ.
اهو شامل ڪرڻ ضروري آهي ته رپورٽون حاصل ڪرڻ لاء، توهان کي pg_stat_activity ۽ pg_stat_statements نظرين جي وچ ۾ هڪ ڪنيڪشن ٺاهڻ جي ضرورت آهي. جدولن کي ڳنڍيو ويو آهي 'queryid' ڪالمن کي شامل ڪرڻ سان 'history_pg_stat_activity'، 'archive_pg_stat_activity' جدولن ۾. ڪالمن جي قيمت شامل ڪرڻ جو طريقو هن مضمون جي دائري کان ٻاهر آهي ۽ هتي بيان ڪيو ويو آهي - pg_stat_statements + pg_stat_activity + loq_query = pg_ash؟ .
سوالن لاءِ TOTAL CPU وقت
درخواست:
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
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
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
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
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
ڏيکاريل بنيادي سوالن ۽ نتيجي ۾ رپورٽون اڳ ۾ ئي زندگي کي تمام آسان بڻائي ٿي جڏهن ڪارڪردگي جي واقعن جو تجزيو ڪيو وڃي.
بنيادي سوالن جي بنياد تي، توهان هڪ رپورٽ حاصل ڪري سگهو ٿا جيڪا مبہم طور تي Oracle's AWR وانگر آهي. خلاصو رپورٽ جو مثال