{"id":38232,"date":"2019-10-31T22:22:28","date_gmt":"2019-10-31T19:22:28","guid":{"rendered":"https:\/\/prohoster.info\/blog\/odin-iz-metodov-polucheniya-istorii-blokirovok-v-postgresql\/"},"modified":"2019-10-31T22:22:28","modified_gmt":"2019-10-31T19:22:28","slug":"odin-iz-metodov-polucheniya-istorii-blokirovok-v-postgresql","status":"publish","type":"post","link":"https:\/\/prohoster.info\/it\/blog\/administrirovanie\/odin-iz-metodov-polucheniya-istorii-blokirovok-v-postgresql","title":{"rendered":"Uno dei metodi per ottenere la cronologia dei blocchi in PostgreSQL","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"

Continuazione dell'articolo «Tentativo di creare un equivalente di ASH per PostgreSQL <\/a><\/noindex>\u00ab<\/p>\n

In questo articolo verr\u00e0 esaminato e mostrato, attraverso query specifiche ed esempi, quale utile informazione si pu\u00f2 ottenere grazie alla cronologia della vista pg_locks.<\/p>\n

Attenzione.
\nA causa della novit\u00e0 dell'argomento e del periodo di test incompleto, l'articolo potrebbe contenere errori. Critiche e osservazioni sono benvenute e attese.<\/p><\/blockquote>\n

<\/a><\/noindex><\/p>\n

Dati di input<\/h2>\n

<\/p>\n

Cronologia della vista pg_locks<\/h3>\n

\narchive_locking<\/b><\/p>\n

CREATE TABLE archive_locking \n(       timepoint timestamp without time zone ,\n\tlocktype text ,\n\trelation oid ,\n\tmode text ,\n\ttid xid ,\n\tvtid text ,\n\tpid integer ,\n\tblocking_pids integer[] ,\n\tgranted boolean ,\n        queryid bigint \n);<\/code><\/pre>\n
\nIn sostanza, la tabella \u00e8 analoga alla tabella archive_pg_stat_activity<\/b>, descritta pi\u00f9 dettagliatamente qui \u2014 pg_stat_statements + pg_stat_activity + loq_query = pg_ash? <\/a><\/noindex> e qui \u2014 Tentativo di creare un analogo di ASH per PostgreSQL.<\/a><\/noindex><\/p>\n
Per popolare la colonna queryid<\/b> si utilizza la funzione <\/p>\n
update_history_locking_by_queryid<\/b><\/p>\n
--update_history_locking_by_queryid.sql\nCREATE OR REPLACE FUNCTION update_history_locking_by_queryid() RETURNS boolean AS $$\nDECLARE\n  result boolean ;\n  current_minute double precision ; \n  \n  start_minute integer ;\n  finish_minute integer ;\n  \n  start_period timestamp without time zone ;\n  finish_period timestamp without time zone ;\n  \n  lock_rec record ; \n  endpoint_rec record ; \n  \n  current_hour_diff double precision ;\nBEGIN\n  RAISE NOTICE '***update_history_locking_by_queryid';\n  \n  result = TRUE ;\n  \n  current_minute = extract ( minute from now() );\n\n  SELECT * FROM endpoint WHERE is_need_monitoring\n  INTO endpoint_rec ;\n  \n  current_hour_diff = endpoint_rec.hour_diff ;\n  \n  IF current_minute < 5 \n  THEN\n\tRAISE NOTICE 'L'ora attuale \u00e8 inferiore a 5 minuti.';\n\t\n\tstart_period = date_trunc('hour',now()) + (current_hour_diff * interval '1 hour');\n    finish_period = start_period - interval '5 minutes' ;\n  ELSE \n    finish_minute =  extract ( minute from now() ) \/ 5 ;\n    start_minute =  finish_minute - 1 ;\n  \n    start_period = date_trunc('hour',now()) + interval '1 minute'*start_minute*5+(current_hour_diff * interval '1 hour');\n    finish_period = date_trunc('hour',now()) + interval '1 minute'*finish_minute*5+(current_hour_diff * interval '1 hour') ;\n    \n  END IF ;  \n  \n  RAISE NOTICE 'start_period = %', start_period;\n  RAISE NOTICE 'finish_period = %', finish_period;\n\n\tFOR lock_rec IN   \n\tWITH act_queryid AS\n\t (\n\t\tSELECT \n\t\t\t\tpid , \n\t\t\t\ttimepoint ,\n\t\t\t\tquery_start AS started ,\t\t\t\n\t\t\t\tMAX(timepoint) OVER (PARTITION BY pid ,\tquery_start   ) AS finished ,\t\t\t\n\t\t\t\tqueryid \n\t\tFROM \n\t\t\t\tactivity_hist.history_pg_stat_activity \t\t\t\n\t\tWHERE \t\t\t\n\t\t\t\ttimepoint BETWEEN start_period and \n\t\t\t\t\t\t\t\t  finish_period\n\t\tGROUP BY \n\t\t\t\tpid , \n\t\t\t\ttimepoint ,  \n\t\t\t\tquery_start ,\n\t\t\t\tqueryid \n\t ),\n\t lock_pids AS\n\t\t(\n\t\t\tSELECT\n\t\t\t\thl.pid , \n\t\t\t\thl.locktype  ,\n\t\t\t\thl.mode ,\n\t\t\t\thl.timepoint , \n\t\t\t\tMIN ( timepoint ) OVER (PARTITION BY pid , locktype  ,mode ) as started \n\t\t\tFROM \n\t\t\t\tactivity_hist.history_locking hl\n\t\t\tWHERE \n\t\t\t\thl.timepoint between start_period and \n\t\t\t\t\t\t\t\t     finish_period\n\t\t\tGROUP BY \n\t\t\t\thl.pid , \n\t\t\t\thl.locktype  ,\n\t\t\t\thl.mode ,\n\t\t\t\thl.timepoint \n\t\t)\n\tSELECT \n\t\tlp.pid , \n\t\tlp.locktype  ,\n\t\tlp.mode ,\n\t\tlp.timepoint ,     \n\t\taq.queryid \n\tFROM lock_pids \tlp LEFT OUTER JOIN act_queryid aq ON ( lp.pid = aq.pid AND lp.started BETWEEN aq.started AND aq.finished )\n\tWHERE aq.queryid IS NOT NULL \n\tGROUP BY  \n\t\tlp.pid , \n\t\tlp.locktype  ,\n\t\tlp.mode ,\n\t\tlp.timepoint , \n\t\taq.queryid\n\tLOOP\n\t\tUPDATE activity_hist.history_locking SET queryid = lock_rec.queryid \n\t\tWHERE pid = lock_rec.pid AND locktype = lock_rec.locktype AND mode = lock_rec.mode AND timepoint = lock_rec.timepoint ;\t\n\tEND LOOP;    \n  \n  RETURN result ;\nEND\n$$ LANGUAGE plpgsql;<\/code><\/pre>\n
\nSpiegazione:<\/b> il valore della colonna queryid viene aggiornato nella tabella history_locking e successivamente, quando viene creata una nuova sezione per la tabella archive_locking, il valore verr\u00e0 salvato nei valori storici. <\/p>\n
Output<\/h2>\n
\nInformazioni generali sui processi nel loro complesso.<\/p>\n
IN ATTESA DI LOCK PER TIPI DI LOCK<\/h3>\n
\nRichiesta<\/b><\/p>\n
CON\nt COME\n(\n\tSELEZIONA \n\t\tlocktype  ,\n\t\tmode ,\n\t\tcount(*) as total \n\tDA \n\t\tactivity_hist.archive_locking\n\tDOVE \n\t\ttimepoint tra pg_stat_history_begin+(current_hour_diff * interval '1 ora') E pg_stat_history_end+(current_hour_diff * interval '1 ora') E \n\t\tNON granted\n\tRAGGRUPPA PER \n\t\tlocktype  ,\n\t\tmode  \n)\nSELEZIONA \n\tlocktype  ,\n\tmode ,\n\ttotal * interval '1 secondo' come durata\t\t\t\nDA t \t\t\nORDINA PER 3 DESC <\/code><\/pre>\n
\nEsempio<\/b><\/p>\n
| IN ATTESA DI LOCK PER TIPI DI LOCK\n+--------------------+------------------------------+--------------------\n|            locktype|                          mode|            durata\n+--------------------+------------------------------+--------------------\n|       transactionid|                     ShareLock|            19:39:26\n|               tuple|           AccessExclusiveLock|            00:03:35\n+--------------------+------------------------------+--------------------\n<\/pre>\n
<\/p>\n
PRELIEVI DI LOCK PER TIPI DI LOCK<\/h3>\n
\nRichiesta<\/b><\/p>\n
CON\nt COME\n(\n\tSELEZIONA \n\t\tlocktype  ,\n\t\tmode ,\n\t\tcount(*) as total \n\tDA \n\t\tactivity_hist.archive_locking\n\tDOVE \n\t\ttimepoint tra pg_stat_history_begin+(current_hour_diff * interval '1 ora') E pg_stat_history_end+(current_hour_diff * interval '1 ora') E \n\t\tgranted\n\tRAGGRUPPA PER \n\t\tlocktype  ,\n\t\tmode  \n)\nSELEZIONA \n\tlocktype  ,\n\tmode ,\n\ttotal * interval '1 secondo' come durata\t\t\t\nDA t \t\t\nORDINA PER 3 DESC <\/code><\/pre>\n
\nEsempio<\/b><\/p>\n
| PRESA DE LOCK DA LOCKTYPE\n+--------------------+------------------------------+--------------------\n|            locktype|                          mode|            durata\n+--------------------+------------------------------+--------------------\n|            relation|              RowExclusiveLock|            51:11:10\n|          virtualxid|                 ExclusiveLock|            48:10:43\n|       transactionid|                 ExclusiveLock|            44:24:53\n|            relation|               AccessShareLock|            20:06:13\n|               tuple|           AccessExclusiveLock|            17:58:47\n|               tuple|                 ExclusiveLock|            01:40:41\n|            relation|      ShareUpdateExclusiveLock|            00:26:41\n|              object|              RowExclusiveLock|            00:00:01\n|       transactionid|                     ShareLock|            00:00:01\n|              extend|                 ExclusiveLock|            00:00:01\n+--------------------+------------------------------+--------------------\n<\/pre>\n
\nInformazioni dettagliate sui queryid specifici delle richieste<\/p>\n
IN ATTESA DI LOCK DA LOCKTYPE PER QUERYID<\/h3>\n
\nRichiesta<\/b><\/p>\n
CON\nlt COME\n(\n\tSELEZIONA\n\t\tpid , \n\t\tlocktype ,\n\t\tmode ,\n\t\ttimepoint , \n\t\tqueryid , \n\t\tblocking_pids ,\n                MIN ( timepoint ) OVER (PARTIZIONE PER pid , locktype ,mode ) as iniziato  \n\tDA \n\t\tactivity_hist.archive_locking\n\tDOVE \n\t\ttimepoint tra pg_stat_history_begin+(current_hour_diff * intervallo '1 ora') E \n\t\t\t                  pg_stat_history_end+(current_hour_diff * intervallo '1 ora') E \n\t\tNON concesso E\n\t       queryid \u00c8 NON NULL \n\tRAGGRUPPA PER \n\t        pid , \n\t\tlocktype ,\n\t\tmode ,\n\t\ttimepoint ,\n\t\tqueryid ,\n\t\tblocking_pids \n)\nSELEZIONA \n        lt.pid , \n\tlt.locktype ,\n\tlt.mode ,\t\t\t\n        lt.iniziato ,\n\tlt.queryid ,\n\tlt.blocking_pids ,\n\tCOUNT(*)  * intervallo '1 secondo'\t come durata\t\t\nDA lt \t\nRAGGRUPPA PER \n\tlt.pid , \n        lt.locktype ,\n\tlt.mode ,\t\t\t\n        lt.iniziato ,\n        lt.queryid ,\n\tlt.blocking_pids \nORDINA PER 4<\/code><\/pre>\n
\nEsempio<\/b><\/p>\n
| IN ATTESA DI BLOCCO PER TIPO DI BLOCCO PER ID QUERY\n+----------+-------------------------+--------------------+------------------------------+--------------------+--------------------+--------------------\n|       pid|                 locktype|                mode|                       started|             queryid|       blocking_pids|            duration\n+----------+-------------------------+--------------------+------------------------------+--------------------+--------------------+--------------------\n|     11288|            transactionid|           ShareLock|    2019-09-17 10:00:00.302936|  389015618226997618|             {11092}|            00:03:34\n|     11626|            transactionid|           ShareLock|    2019-09-17 10:00:21.380921|  389015618226997618|             {12380}|            00:00:29\n|     11626|            transactionid|           ShareLock|    2019-09-17 10:00:21.380921|  389015618226997618|             {11092}|            00:03:25\n|     11626|            transactionid|           ShareLock|    2019-09-17 10:00:21.380921|  389015618226997618|             {12213}|            00:01:55\n|     11626|            transactionid|           ShareLock|    2019-09-17 10:00:21.380921|  389015618226997618|             {12751}|            00:00:01\n|     11629|            transactionid|           ShareLock|    2019-09-17 10:00:24.331935|  389015618226997618|             {11092}|            00:03:22\n|     11629|            transactionid|           ShareLock|    2019-09-17 10:00:24.331935|  389015618226997618|             {12007}|            00:00:01\n|     12007|            transactionid|           ShareLock|    2019-09-17 10:05:03.327933|  389015618226997618|             {11629}|            00:00:13\n|     12007|            transactionid|           ShareLock|    2019-09-17 10:05:03.327933|  389015618226997618|             {11092}|            00:01:10\n|     12007|            transactionid|           ShareLock|    2019-09-17 10:05:03.327933|  389015618226997618|             {11288}|            00:00:05\n|     12213|            transactionid|           ShareLock|    2019-09-17 10:06:07.328019|  389015618226997618|             {12007}|            00:00:10<\/pre>\n
<\/p>\n
PRENDERE LOCK DA LOCKTYPE PER QUERYID<\/h3>\n
\nRichiesta<\/b><\/p>\n
CON\nlt COME\n(\n\tSELEZIONA\n\t\tpid , \n\t\tlocktype  ,\n\t\tmode ,\n\t\ttimepoint , \n\t\tqueryid , \n\t\tblocking_pids ,\n                MIN ( timepoint ) OVER (PARTITION BY pid , locktype  ,mode ) come iniziato  \n\tDA \n\t\tactivity_hist.archive_locking\n\tDOVE \n\t\ttimepoint tra pg_stat_history_begin+(current_hour_diff * interval '1 hour') E \n\t\t\t                  pg_stat_history_end+(current_hour_diff * interval '1 hour') E \n\t\tconcesso E\n\t\tqueryid \u00c8 NON NULL \n\tGROUP BY \n\t        pid , \n\t\tlocktype  ,\n\t\tmode ,\n\t\ttimepoint ,\n\t\tqueryid ,\n\t\tblocking_pids \n)\nSELEZIONA \n        lt.pid , \n\tlt.locktype  ,\n\tlt.mode ,\t\t\t\n        lt.iniziato ,\n\tlt.queryid  ,\n\tlt.blocking_pids ,\n\tCOUNT(*)  * interval '1 second'\t come durata\t\t\t\nDA lt \t\nGROUP BY \n\tlt.pid , \n\tlt.locktype  ,\n\tlt.mode ,\t\t\t\n        lt.iniziato ,\n\tlt.queryid ,\n\tlt.blocking_pids \nORDINA PER 4<\/code><\/pre>\n
\nEsempio<\/b><\/p>\n
| RICERCA LOCKS PER TIPO DI LOCKS PER QUERYID\n+----------+-------------------------+--------------------+------------------------------+--------------------+--------------------+--------------------\n|       pid|                 locktype|                mode|                       started|             queryid|       blocking_pids|            duration\n+----------+-------------------------+--------------------+------------------------------+--------------------+--------------------+--------------------\n|     11288|                 relation|    RowExclusiveLock|    2019-09-17 10:00:00.302936|  389015618226997618|             {11092}|            00:03:34\n|     11092|            transactionid|       ExclusiveLock|    2019-09-17 10:00:00.302936|  389015618226997618|                  {}|            00:03:34\n|     11288|                 relation|    RowExclusiveLock|    2019-09-17 10:00:00.302936|  389015618226997618|                  {}|            00:00:10\n|     11092|                 relation|    RowExclusiveLock|    2019-09-17 10:00:00.302936|  389015618226997618|                  {}|            00:03:34\n|     11092|               virtualxid|       ExclusiveLock|    2019-09-17 10:00:00.302936|  389015618226997618|                  {}|            00:03:34\n|     11288|               virtualxid|       ExclusiveLock|    2019-09-17 10:00:00.302936|  389015618226997618|             {11092}|            00:03:34\n|     11288|            transactionid|       ExclusiveLock|    2019-09-17 10:00:00.302936|  389015618226997618|             {11092}|            00:03:34\n|     11288|                    tuple| AccessExclusiveLock|    2019-09-17 10:00:00.302936|  389015618226997618|             {11092}|            00:03:34<\/pre>\n
\nUtilizzo della cronologia delle blocchi nell'analisi degli incidenti di prestazioni.<\/b><\/p>\n
    \n
  1. La richiesta con queryid=389015618226997618 eseguita dal processo con pid=11288 ha atteso un blocco a partire dal 2019-09-17 10:00:00 per 3 minuti.<\/li>\n
  2. Il blocco \u00e8 stato mantenuto dal processo con pid=11092.<\/li>\n
  3. Il processo con pid=11092, eseguendo la richiesta con queryid=389015618226997618 a partire dal 2019-09-17 10:00:00, ha mantenuto il blocco per 3 minuti.<\/li>\n<\/ol>\n
    <\/p>\n
    Risultato<\/h2>\n
    \nOra, spero, inizia la parte pi\u00f9 interessante e utile: la raccolta di statistiche e l'analisi dei casi sulla storia delle attese e dei blocchi. <\/p>\n
    In prospettiva, voglio credere che si riuscir\u00e0 a ottenere un insieme di alcune note simili a quelle del metalink di Oracle.<\/p>\n
    In effetti, proprio per questo motivo la metodologia utilizzata viene presentata il pi\u00f9 rapidamente possibile per la conoscenza generale.<\/p>\n
    Cercher\u00f2 di pubblicare il progetto su github nel pi\u00f9 breve tempo possibile.
    \n
    Fonte: habr.com<\/a><\/p>","protected":false,"gt_translate_keys":[{"key":"rendered","format":"html"}]},"excerpt":{"rendered":"
    \u041f\u0440\u043e\u0434\u043e\u043b\u0436\u0435\u043d\u0438\u0435 \u0441\u0442\u0430\u0442\u044c\u0438 «\u041f\u043e\u043f\u044b\u0442\u043a\u0430 \u0441\u043e\u0437\u0434\u0430\u0442\u044c \u0430\u043d\u0430\u043b\u043e\u0433 ASH \u0434\u043b\u044f PostgreSQL «. \u0412 \u0441\u0442\u0430\u0442\u044c\u0435 \u0431\u0443\u0434\u0435\u0442 \u0440\u0430\u0441\u0441\u043c\u043e\u0442\u0440\u0435\u043d\u043e \u0438 \u043f\u043e\u043a\u0430\u0437\u0430\u043d\u043e \u043d\u0430 \u043a\u043e\u043d\u043a\u0440\u0435\u0442\u043d\u044b\u0445 \u0437\u0430\u043f\u0440\u043e\u0441\u0430\u0445 \u0438 \u043f\u0440\u0438\u043c\u0435\u0440\u0430\u0445 \u2014 \u043a\u0430\u043a\u0443\u044e \u0436\u0435 \u043f\u043e\u043b\u0435\u0437\u043d\u0443\u044e \u0438\u043d\u0444\u043e\u0440\u043c\u0430\u0446\u0438\u044e \u043c\u043e\u0436\u043d\u043e \u043f\u043e\u043b\u0443\u0447\u0438\u0442\u044c \u0441 \u043f\u043e\u043c\u043e\u0449\u044c\u044e \u0438\u0441\u0442\u043e\u0440\u0438\u0438 \u043f\u0440\u0435\u0434\u0441\u0442\u0430\u0432\u043b\u0435\u043d\u0438\u044f pg_locks. \u041f\u0440\u0435\u0434\u0443\u043f\u0440\u0435\u0436\u0434\u0435\u043d\u0438\u0435. \u0412 \u0441\u0432\u044f\u0437\u0438 \u0441 \u043d\u043e\u0432\u0438\u0437\u043d\u043e\u0439 \u0442\u0435\u043c\u044b \u0438 \u043d\u0435\u0437\u0430\u0432\u0435\u0440\u0448\u0435\u043d\u0438\u0435\u043c \u043f\u0435\u0440\u0438\u043e\u0434\u0430 \u0442\u0435\u0441\u0442\u0438\u0440\u043e\u0432\u0430\u043d\u0438\u044f, \u0441\u0442\u0430\u0442\u044c\u044f \u043c\u043e\u0436\u0435\u0442 \u0441\u043e\u0434\u0435\u0440\u0436\u0430\u0442\u044c \u043e\u0448\u0438\u0431\u043a\u0438. \u041a\u0440\u0438\u0442\u0438\u043a\u0430 \u0438 \u0437\u0430\u043c\u0435\u0447\u0430\u043d\u0438\u044f \u0432\u0441\u044f\u0447\u0435\u0441\u043a\u0438 \u043f\u0440\u0438\u0432\u0435\u0442\u0441\u0442\u0432\u0443\u044e\u0442\u0441\u044f \u0438 \u043e\u0436\u0438\u0434\u0430\u044e\u0442\u0441\u044f. \u0412\u0445\u043e\u0434\u043d\u044b\u0435 \u0434\u0430\u043d\u043d\u044b\u0435 […]<\/p>\n","protected":false,"gt_translate_keys":[{"key":"rendered","format":"html"}]},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[688],"tags":[],"class_list":["post-38232","post","type-post","status-publish","format-standard","hentry","category-administrirovanie"],"aioseo_notices":[],"aioseo_head":"\n\t\t\n\t\n\t\n\t\n\t\n\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\n","aioseo_head_json":{"title":"\ud83e\udd47Uno dei metodi per ottenere la storia dei blocchi in PostgreSQL | ProHoster","description":"Continuazione dell'articolo \"Tentativo di creare un analogo di ASH per PostgreSQL\". Nell'articolo verranno esaminati e mostrati richieste specifiche e.","canonical_url":"https:\/\/prohoster.info\/it\/blog\/administrirovanie\/odin-iz-metodov-polucheniya-istorii-blokirovok-v-postgresql","robots":"max-image-preview:large","keywords":"","webmasterTools":{"miscellaneous":""},"schema":null,"og:locale":"it_IT","og:site_name":"ProHoster | \u041a\u0443\u043f\u0438\u0442\u044c \u043d\u0430\u0434\u0435\u0436\u043d\u044b\u0439 \u0445\u043e\u0441\u0442\u0438\u043d\u0433 \u0434\u043b\u044f \u0441\u0430\u0439\u0442\u043e\u0432 \u0441 \u0437\u0430\u0449\u0438\u0442\u043e\u0439 \u043e\u0442 DDoS, VPS VDS \u0441\u0435\u0440\u0432\u0435\u0440\u044b","og:type":"article","og:title":"\ud83e\udd47\u041e\u0434\u0438\u043d \u0438\u0437 \u043c\u0435\u0442\u043e\u0434\u043e\u0432 \u043f\u043e\u043b\u0443\u0447\u0435\u043d\u0438\u044f \u0438\u0441\u0442\u043e\u0440\u0438\u0438 \u0431\u043b\u043e\u043a\u0438\u0440\u043e\u0432\u043e\u043a \u0432 PostgreSQL | ProHoster","og:description":"\u041f\u0440\u043e\u0434\u043e\u043b\u0436\u0435\u043d\u0438\u0435 \u0441\u0442\u0430\u0442\u044c\u0438 "\u041f\u043e\u043f\u044b\u0442\u043a\u0430 \u0441\u043e\u0437\u0434\u0430\u0442\u044c \u0430\u043d\u0430\u043b\u043e\u0433 ASH \u0434\u043b\u044f PostgreSQL ". \u0412 \u0441\u0442\u0430\u0442\u044c\u0435 \u0431\u0443\u0434\u0435\u0442 \u0440\u0430\u0441\u0441\u043c\u043e\u0442\u0440\u0435\u043d\u043e \u0438 \u043f\u043e\u043a\u0430\u0437\u0430\u043d\u043e \u043d\u0430 \u043a\u043e\u043d\u043a\u0440\u0435\u0442\u043d\u044b\u0445 \u0437\u0430\u043f\u0440\u043e\u0441\u0430\u0445 \u0438.","og:url":"https:\/\/prohoster.info\/it\/blog\/administrirovanie\/odin-iz-metodov-polucheniya-istorii-blokirovok-v-postgresql","og:image":"https:\/\/prohoster.info\/wp-content\/uploads\/2021\/11\/logo-350.jpg","og:image:secure_url":"https:\/\/prohoster.info\/wp-content\/uploads\/2021\/11\/logo-350.jpg","og:image:width":350,"og:image:height":350,"article:published_time":"2019-10-31T19:22:28+00:00","article:modified_time":"2019-10-31T19:22:28+00:00","article:publisher":"https:\/\/www.facebook.com\/prohoster","article:author":"https:\/\/www.facebook.com\/prohoster"},"aioseo_meta_data":{"post_id":"38232","title":null,"description":null,"keywords":null,"keyphrases":null,"primary_term":null,"canonical_url":null,"og_title":null,"og_description":null,"og_object_type":"default","og_image_type":"default","og_image_url":null,"og_image_width":null,"og_image_height":null,"og_image_custom_url":null,"og_image_custom_fields":null,"og_video":null,"og_custom_url":null,"og_article_section":null,"og_article_tags":null,"twitter_use_og":false,"twitter_card":"default","twitter_image_type":"default","twitter_image_url":null,"twitter_image_custom_url":null,"twitter_image_custom_fields":null,"twitter_title":null,"twitter_description":null,"schema":{"blockGraphs":[],"customGraphs":[],"default":{"data":{"Article":[],"Course":[],"Dataset":[],"FAQPage":[],"Movie":[],"Person":[],"Product":[],"ProductReview":[],"Car":[],"Recipe":[],"Service":[],"SoftwareApplication":[],"WebPage":[]},"graphName":"","isEnabled":true},"graphs":[]},"schema_type":null,"schema_type_options":null,"pillar_content":false,"robots_default":true,"robots_noindex":false,"robots_noarchive":false,"robots_nosnippet":false,"robots_nofollow":false,"robots_noimageindex":false,"robots_noodp":false,"robots_notranslate":false,"robots_max_snippet":null,"robots_max_videopreview":null,"robots_max_imagepreview":"large","priority":null,"frequency":null,"local_seo":null,"seo_analyzer_scan_date":"2026-01-23 21:03:19","breadcrumb_settings":null,"limit_modified_date":false,"reviewed_by":null,"ai":null,"created":"2021-03-01 01:13:22","updated":"2026-01-23 21:03:19","focus_keyword":null,"additional_keywords":null,"truseo_locale":null},"gt_translate_keys":[{"key":"link","format":"url"}],"_links":{"self":[{"href":"https:\/\/prohoster.info\/it\/wp-json\/wp\/v2\/posts\/38232","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/prohoster.info\/it\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/prohoster.info\/it\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/prohoster.info\/it\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/prohoster.info\/it\/wp-json\/wp\/v2\/comments?post=38232"}],"version-history":[{"count":0,"href":"https:\/\/prohoster.info\/it\/wp-json\/wp\/v2\/posts\/38232\/revisions"}],"wp:attachment":[{"href":"https:\/\/prohoster.info\/it\/wp-json\/wp\/v2\/media?parent=38232"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/prohoster.info\/it\/wp-json\/wp\/v2\/categories?post=38232"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/prohoster.info\/it\/wp-json\/wp\/v2\/tags?post=38232"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}