ProHoster > Blog > administración > Un intento de crear un análogo de ASH para PostgreSQL

Un intento de crear un análogo de ASH para PostgreSQL

Formulación del problema

Para optimizar las consultas de PostgreSQL, es muy necesaria la capacidad de analizar el historial de actividad, en particular, esperas, bloqueos y estadísticas de tablas.

Oportunidades disponibles

Herramienta de análisis de carga de trabajo histórica o "AWR para Postgres": una solución muy interesante, pero no hay historial de pg_stat_activity y pg_locks.

extensión pgsentinel :
«Toda la información acumulada se almacena solo en la RAM, y la cantidad de memoria consumida está regulada por el número de los últimos registros almacenados.

Se agrega el campo queryid: el mismo queryid de la extensión pg_stat_statements (se requiere preinstalación).«

Esto, por supuesto, ayudaría mucho, pero lo más problemático es el primer punto”.Toda la información acumulada se almacena solo en la RAM. ", es decir. hay un impacto en la base objetivo. Además, no hay historial de bloqueos ni estadísticas de tablas. Aquellos. la solución es en general incompleta: “Aún no existe ningún paquete listo para instalar. Se sugiere descargar las fuentes y montar la biblioteca usted mismo. Primero debe instalar el paquete "devel" para su servidor y establecer la ruta a pg_config en la variable PATH..

En general, hay mucho alboroto y, en el caso de bases de datos de producción serias, es posible que no sea posible hacer nada con el servidor. Necesitamos volver a inventar algo propio.

Advertencia.

Debido al volumen bastante grande y al período de prueba incompleto, el artículo es principalmente de carácter informativo, más bien como un conjunto de tesis y resultados intermedios.
Más adelante se preparará material más detallado, por partes.

Borrador de requisitos para la solución.

Es necesario desarrollar una herramienta que permita almacenar:

pg_stat_activity ver historial
Historial de bloqueo de sesión usando la vista pg_locks

Requisito de solución–minimizar el impacto en la base de datos de destino.

Idea general– el agente de recopilación de datos no se inicia en la base de datos de destino, sino en la base de datos de seguimiento como un servicio systemd. Sí, es posible que se pierdan algunos datos, pero esto no es crítico para los informes, pero no tiene ningún impacto en la base de datos de destino en términos de memoria y espacio en disco. Y en el caso de utilizar un grupo de conexiones, el impacto en los procesos de los usuarios es mínimo.

Etapas de implementación

1.Mesas de servicio

Se utiliza un esquema separado para almacenar tablas, para no complicar el análisis de las tablas principales utilizadas.

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

Importante: El esquema no se crea en la base de datos de destino, sino en la base de datos de supervisión.

pg_stat_activity ver historial

La tabla pg_stat_activity se utiliza para almacenar instantáneas actuales de la vista.

actividad_hist.history_pg_stat_actividad :

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

Para acelerar la inserción, sin índices ni restricciones.

Para almacenar el historial en sí, se utiliza una tabla particionada:

actividad_hist.archive_pg_stat_actividad :

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

Dado que en este caso no existen requisitos de velocidad de inserción, se han creado algunos índices para acelerar la creación de informes.

Historial de bloqueo de sesiones

Se utiliza una tabla para almacenar instantáneas actuales de los bloqueos de sesión:

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

Además, para acelerar la inserción, no existen índices ni restricciones.

Para almacenar el historial en sí, se utiliza una tabla particionada:

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

Dado que en este caso no existen requisitos de velocidad de inserción, se han creado algunos índices para acelerar la creación de informes.

2.Rellenar el historial actual

Para recopilar instantáneas de vistas directamente, se utiliza un script bash que ejecuta la función plpgsql.

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 La función dblink accede a vistas en la base de datos de destino e inserta filas en tablas de servicio en la base de datos de monitoreo.

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;

Para recopilar instantáneas de vistas, se utilizan el servicio systemd y dos scripts:

pg_actividad_actual.servicio

# /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_actividad_actual.temporizador

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

Asignar derechos a los scripts:
# chmod 755 pg_current_activity.timer
# chmod 755 pg_current_activity.servicio

Comencemos el servicio:
# systemctl daemon-reload
# systemctl inicia pg_current_activity.service

De este modo, el historial de visualizaciones se recopila en forma de instantáneas segundo a segundo. Por supuesto, si todo se deja como está, las mesas aumentarán rápidamente de tamaño y será imposible realizar un trabajo más o menos productivo.

Es necesario organizar el archivo de datos.

3. Archivar el historial

Para archivar, se utilizan archivos de tablas particionadas*.

Se crean nuevas particiones cada hora, mientras que los datos antiguos se eliminan de las tablas de historial*, por lo que el tamaño de las tablas de historial* no cambia mucho y la velocidad de inserción no se degrada con el tiempo.

La creación de nuevas secciones se realiza mediante la función plpgsql Activity_hist.archive_current_activity. El algoritmo de trabajo es muy simple (usando el ejemplo de la sección para la tabla archive_pg_stat_activity).

Crea y completa una nueva sección

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

Creando índices

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

Eliminar datos antiguos de la tabla History_pg_stat_activity

DELETE 
FROM 	activity_hist.history_pg_stat_activity
WHERE 	timepoint < partition_max_range;

Por supuesto, de vez en cuando, las secciones antiguas se eliminan por considerarlas innecesarias.

Informes básicos

En realidad, ¿por qué se hace todo esto? Para obtener informes que recuerdan vagamente al AWR de Oracle.

Es importante agregar que para recibir informes, es necesario establecer una conexión entre las vistas pg_stat_activity y pg_stat_statements. Las tablas se vinculan agregando una columna 'queryid' a las tablas 'history_pg_stat_activity', 'archive_pg_stat_activity'. El método para agregar un valor de columna está más allá del alcance de este artículo y se describe aquí: pg_stat_statements + pg_stat_activity + loq_query = pg_ash? .

TIEMPO TOTAL DE CPU PARA CONSULTAS

Pedido :

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

Ejemplo:

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

TIEMPO TOTAL DE ESPERAS PARA CONSULTAS

Pedido :

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

Ejemplo:

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

ESPERAS POR CONSULTAS

Peticiones:

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

Ejemplo:

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

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

HISTORIAL DE PROCESOS BLOQUEADOS

Solicitud:

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

Ejemplo:

-------------------------------------------------- -------------------------------------------------- --------------------------------- | HISTORIAL DE PROCESOS BLOQUEADOS +-----+----------+-----+-------- --+------------ --------+--------------------+----- --------------- +------------------- | #| pido| iniciado| duración| bloqueo_pids| relación| modo| tipo de bloqueo +----------+----------+-----+---------- +--------- --+-----------+------- -------------+----- -------------- | 1| 26224| 2019-09-02 19:32:16| 00:01:45| {26211}| 16541| AccesoCompartirBloqueo| relación | 2| 26390| 2019-09-02 19:34:03| 00:00:53| {26211}| 16541| AccesoCompartirBloqueo| relación | 3| 26391| 2019-09-02 19:34:03| 00:00:53| {26211}| 16541| AccesoCompartirBloqueo| relación | 4| 26531| 2019-09-02 19:35:27| 00:00:12| {26211}| 16541| AccesoCompartirBloqueo| relación | 5| 27284| 2019-09-02 19:44:02| 00:00:19| {27276}| 16541| AccesoCompartirBloqueo| relación | 6| 27283| 2019-09-02 19:44:02| 00:00:19| {27276}| 16541| AccesoCompartirBloqueo| relación | 7| 27286| 2019-09-02 19:44:02| 00:00:19| {27276}| 16541| AccesoCompartirBloqueo| relación | 8| 27423| 2019-09-02 19:45:24| 00:00:12| {27394}| 16541| AccesoCompartirBloqueo| relación | 9| 27648| 2019-09-02 19:48:06| 00:00:20| {27647}| 16541| AccesoCompartirBloqueo| relación | 10| 27650| 2019-09-02 19:48:06| 00:00:20| {27647}| 16541| AccesoCompartirBloqueo| relación | 11| 27735| 2019-09-02 19:49:08| 00:00:06| {27650}| 16541| AccesoExclusivoBloqueo| relación | 12| 28380| 2019-09-02 19:56:03| 00:01:56| {28379}| 16541| AccesoCompartirBloqueo| relación | 13| 28379| 2019-09-02 19:56:03| 00:00:01| 28377| 16541| AccesoExclusivoBloqueo| relación | | | | | 28376| |

HISTORIAL DE PROCESOS DE BLOQUEO

Peticiones:

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

Ejemplo:

-------------------------------------------------- -------------------------------------------------- -------------------------------------------------- ----------------------- HISTORIAL DE PROCESOS DE BLOQUEO +----+----------+------- ---+--------------------+----------+-------------- ------+--------------------+--------------------- - -------+------------------------------------------------ | #| pido| nombre de uso| nombre_aplicación| nombre de datos| iniciado| duración| estado| consulta +----------+----------+----------+-----+ --------- -+--------------------+------------------ --+------ -----------------+---------------- ------- ----------------- | 1| 26211| usuario| psql| tdb1| 2019-09-02 19:31:54| 00:00:04| inactivo| | 2| 26211| usuario| psql| tdb1| 2019-09-02 19:31:58| 00:00:06| inactivo en transacción| comenzar; | 3| 26211| usuario| psql| tdb1| 2019-09-02 19:32:16| 00:01:45| inactivo en transacción| bloquear tabla wafer_data; | 4| 26211| usuario| psql| tdb1| 2019-09-02 19:35:54| 00:01:23| inactivo| comprometerse; | 5| 26211| usuario| psql| tdb1| 2019-09-02 19:38:46| 00:00:02| inactivo en transacción| comenzar; | 6| 26211| usuario| psql| tdb1| 2019-09-02 19:38:54| 00:00:08| inactivo en transacción| bloquear tabla wafer_data; | 7| 26211| usuario| psql| tdb1| 2019-09-02 19:39:08| 00:42:42| inactivo| comprometerse; | 8| 26211| usuario| psql| tdb1| 2019-09-03 07:12:07| 00:00:52| activo| seleccione test_del();

Desarrollo.

Las consultas básicas mostradas y los informes resultantes ya facilitan mucho la vida a la hora de analizar incidencias de rendimiento.
Según consultas básicas, puede obtener un informe que se parece vagamente al AWR de Oracle.
Ejemplo de informe resumido

+------------------------------------------------- ----------------------------------- | INFORME CONSOLIDADO DE ACTIVIDAD Y ESPERAS.

Continuará. Lo siguiente en la fila es la creación de un historial de bloqueos (pg_stat_locks), una descripción más detallada del proceso de llenado de tablas.

Fuente: habr.com

Añadir un comentario