{"id":72875,"date":"2020-03-05T08:42:09","date_gmt":"2020-03-05T05:42:09","guid":{"rendered":"https:\/\/prohoster.info\/blog\/administrirovanie\/zdorove-indeksov-v-postgresql-glazami-java-razrabotchika"},"modified":"2020-03-05T08:42:09","modified_gmt":"2020-03-05T05:42:09","slug":"zdorove-indeksov-v-postgresql-glazami-java-razrabotchika","status":"publish","type":"post","link":"https:\/\/prohoster.info\/sk\/blog\/administrirovanie\/zdorove-indeksov-v-postgresql-glazami-java-razrabotchika","title":{"rendered":"Zdravie indexov v PostgreSQL o\u010dami Java v\u00fdvoj\u00e1ra","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"

Ahoj.<\/p>\n

<\/p>\n

Vol\u00e1m sa Ivan a som Java v\u00fdvoj\u00e1r. Na\u0161\u0165astie, ve\u013ea pracujem s PostgreSQL - zaober\u00e1m sa nastaven\u00edm datab\u00e1z, optimaliz\u00e1ciou \u0161trukt\u00fary a v\u00fdkonnosti a ob\u010das si zahr\u00e1m na DBA cez v\u00edkendy.<\/p>\n

<\/p>\n

V poslednom \u010dase som upratal nieko\u013eko datab\u00e1z v na\u0161ich mikroservisoch a nap\u00edsal java kni\u017enicu pg-index-health<\/a><\/noindex>, ktor\u00e1 u\u013eah\u010duje t\u00fato pr\u00e1cu, \u0161etr\u00ed m\u00f4j \u010das a pom\u00e1ha vyhn\u00fa\u0165 sa niektor\u00fdm be\u017en\u00fdm chyb\u00e1m, ktor\u00fdch sa dop\u00fa\u0161\u0165aj\u00fa v\u00fdvoj\u00e1ri. O tejto kni\u017enici bude dnes re\u010d.<\/p>\n

<\/p>\n

\"Zdravie<\/p>\n

<\/p>\n

Upozornenie<\/h3>\n

<\/p>\n

Hlavn\u00e1 verzia PostgreSQL, s ktorou pracujem, je 10. V\u0161etky SQL dopyty, ktor\u00e9 pou\u017e\u00edvam, s\u00fa taktie\u017e overen\u00e9 na 11. verzii. Minim\u00e1lna podporovan\u00e1 verzia je 9.6.<\/p>\n

<\/p>\n

Pozadie<\/h3>\n

<\/p>\n

V\u0161etko sa to za\u010dalo pred takmer rokom so zvl\u00e1\u0161tnou situ\u00e1ciou: konkurentn\u00e9 vytv\u00e1ranie indexu na pr\u00e1zdnom mieste skon\u010dilo s chybou. Index, ako obvykle, zostal v neplatnom stave v datab\u00e1ze. Anal\u00fdza logov uk\u00e1zala nedostatok temp_file_limit<\/a><\/noindex>. A za\u010dalo sa... Ke\u010f som sa trochu do toho ponoril, objavil som mno\u017estvo probl\u00e9mov v konfigur\u00e1cii datab\u00e1zy a, s vyhrnut\u00fdmi ruk\u00e1vmi a iskrou v o\u010diach, som sa pustil do ich opravovania.<\/p>\n

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

Prv\u00fd probl\u00e9m - predvolen\u00e1 konfigur\u00e1cia<\/h3>\n

<\/p>\n

Mo\u017eno u\u017e v\u0161etk\u00fdm lezie na nervy metafora o Postgres, ktor\u00fd sa d\u00e1 spusti\u0165 na k\u00e1vovare, ale... predvolen\u00e9 nastavenia skuto\u010dne vyvol\u00e1vaj\u00fa mno\u017estvo ot\u00e1zok. Minim\u00e1lne by ste mali venova\u0165 pozornos\u0165 maintenance_work_mem<\/strong>, temp_file_limit<\/strong>, statement_timeout<\/strong> a lock_timeout<\/strong>.<\/p>\n

<\/p>\n

V na\u0161om pr\u00edpade maintenance_work_mem<\/strong> bol predvolen\u00fd na 64 MB, zatia\u013e \u010do temp_file_limit<\/strong> pribli\u017ene 2 GB - proste sme nemali dostatok pam\u00e4te na vytvorenie indexu na ve\u013ekej tabu\u013eke.<\/p>\n

<\/p>\n

Preto som v pg-index-health<\/strong> zhrom\u017edil radu k\u013e\u00fa\u010dov\u00fdch<\/a><\/noindex>, pod\u013ea m\u00f4jho n\u00e1zoru, parametrov, ktor\u00e9 je potrebn\u00e9 nastavi\u0165 pre ka\u017ed\u00fa datab\u00e1zu.<\/p>\n

<\/p>\n

Druh\u00fd probl\u00e9m - duplicovan\u00e9 indexy<\/h3>\n

<\/p>\n

Na\u0161e datab\u00e1zy be\u017eia na SSD diskoch a pou\u017e\u00edvame HA<\/em>-konfigur\u00e1ciu s viacer\u00fdmi d\u00e1tov\u00fdmi centrami, hlavnou hostite\u013eskou a n<\/em>-k\u00fdm po\u010dtom replik. Miesto na disku je pre n\u00e1s ve\u013emi cenn\u00fd zdroj; je rovnako d\u00f4le\u017eit\u00e9 ako v\u00fdkon a spotreba CPU. Preto, na jednej strane, potrebujeme indexy pre r\u00fdchle \u010d\u00edtanie, ale na druhej strane, nechceme vidie\u0165 v datab\u00e1ze zbyto\u010dn\u00e9 indexy, preto\u017ee zaberaj\u00fa miesto a spoma\u013euj\u00fa aktualiz\u00e1ciu d\u00e1t.<\/p>\n

<\/p>\n

A tak, po obnoven\u00ed v\u0161etk\u00fdch neplatn\u00fdch indexov<\/a><\/noindex> a po pozorovan\u00ed predn\u00e1\u0161ok Olega Bartunova<\/a><\/noindex>, rozhodol som sa vykona\u0165 \u201eve\u013ek\u00e9\u201c \u010distenie. Uk\u00e1zalo sa, \u017ee v\u00fdvoj\u00e1ri nemaj\u00fa radi \u010d\u00edtanie dokument\u00e1cie k datab\u00e1zam. Ve\u013emi nemaj\u00fa. Kv\u00f4li tomu vznikaj\u00fa dve typov\u00e9 chyby \u2013 ru\u010dne vytvoren\u00fd index na prim\u00e1rny k\u013e\u00fa\u010d a podobn\u00fd \u201eru\u010dn\u00fd\u201c index na unik\u00e1tny st\u013apec. Ide o to, \u017ee nie s\u00fa potrebn\u00e9 \u2013 Postgres to sprav\u00ed s\u00e1m. Tak\u00e9to indexy je mo\u017en\u00e9 bez ob\u00e1v odstr\u00e1ni\u0165, a na to je k dispoz\u00edcii diagnostika. duplicated_indexes<\/a><\/noindex>.<\/p>\n

<\/p>\n

Tret\u00ed probl\u00e9m \u2013 prekryvaj\u00face sa indexy<\/h3>\n

<\/p>\n

V\u00e4\u010d\u0161ina za\u010d\u00ednaj\u00facich v\u00fdvoj\u00e1rov vytv\u00e1ra indexy na jeden st\u013apec. Postupom \u010dasu, ke\u010f si na to zvykn\u00fa, za\u010dn\u00fa optimalizova\u0165 svoje dotazy a prid\u00e1va\u0165 zlo\u017eitej\u0161ie indexy, ktor\u00e9 obsahuj\u00fa viac st\u013apcov. Tak vznikaj\u00fa indexy na st\u013apce A<\/em>, A+B<\/em>, A+B+C<\/em> a podobne. Prv\u00e9 dva z t\u00fdchto indexov m\u00f4\u017eeme bez ob\u00e1v vyhodi\u0165, preto\u017ee s\u00fa prefixami tretieho. To tie\u017e zna\u010dn\u011b \u0161etr\u00ed miesto na disku a na to je k dispoz\u00edcii diagnostika. intersected_indexes<\/a><\/noindex>.<\/p>\n

<\/p>\n

\u0160tvrt\u00fd probl\u00e9m \u2013 cudz\u00edch k\u013e\u00fa\u010dov bez indexov<\/h3>\n

<\/p>\n

Postgres umo\u017e\u0148uje vytv\u00e1ra\u0165 obmedzenia cudz\u00edch k\u013e\u00fa\u010dov bez ur\u010denia podporuj\u00faceho indexu. V mnoh\u00fdch situ\u00e1ci\u00e1ch to nie je probl\u00e9m a dokonca sa to m\u00f4\u017ee nijako neprejavova\u0165\u2026 Do istej doby\u2026<\/p>\n

<\/p>\n

Tak to bolo aj u n\u00e1s: v istom okamihu sa job, ktor\u00fd sa vykon\u00e1va pod\u013ea rozvrhu a \u010dist\u00ed datab\u00e1zu od testovac\u00edch pr\u00edkazov, za\u010dal \u201ezhroma\u017e\u010fova\u0165\u201c n\u00e1\u0161 master host. CPU a IO i\u0161li do v\u00fd\u0161in, dotazy spoma\u013eovali a preru\u0161ovali sa kv\u00f4li timeoutu, slu\u017eba vracala p\u00e4\u0165stovky. R\u00fdchla anal\u00fdza pg_stat_activity<\/a><\/noindex> uk\u00e1zala, \u017ee viseli dotazy typu:<\/p>\n

<\/p>\n

vymaza\u0165 z <table> kde id v (…)<\/code><\/pre>\n
<\/p>\n
Pri tom index pod\u013ea id v cie\u013eovej tabu\u013eke, samozrejme, bol, a z\u00e1znamy sa mazali na z\u00e1klade podmienky iba vo ve\u013emi malom mno\u017estve. Zdalo sa, \u017ee v\u0161etko by malo fungova\u0165, ale, \u017eia\u013e, nefungovalo.<\/p>\n
<\/p>\n
Na pomoc pri\u0161la \u00fa\u017easn\u00e1 explain analyze<\/strong> a povedala, \u017ee okrem mazania z\u00e1znamov v cie\u013eovej tabu\u013eke prebieha aj kontrola referen\u010dnej integrity, a na jednej z prepojen\u00fdch tabuliek sa t\u00e1to kontrola dost\u00e1va do sequential scan<\/em> kv\u00f4li absencii vhodn\u00e9ho indexu. Tak sa zrodila diagnostika foreign_keys_without_index<\/a><\/noindex>.<\/p>\n
<\/p>\n
Piaty probl\u00e9m \u2013 null hodnota v indexoch<\/h3>\n
<\/p>\n
Pod\u013ea predvolen\u00fdch nastaven\u00ed Postgres zah\u0155\u0148a null hodnoty do btree-indexov, ale tam zvy\u010dajne nie s\u00fa potrebn\u00e9. Preto sa sna\u017e\u00edm tieto null hodnoty odstra\u0148ova\u0165 (diagnostika indexes_with_null_values<\/a><\/noindex>), vytv\u00e1ran\u00edm \u010diasto\u010dn\u00fdch indexov na nullable-st\u013apce typu where  is not null<\/code>. T\u00fdmto sp\u00f4sobom sa mi podarilo zmen\u0161i\u0165 ve\u013ekos\u0165 jedn\u00e9ho z na\u0161ich indexov z 1877 MB na 16 KB. A v jednom z na\u0161ich slu\u017eieb sa celkov\u00e1 ve\u013ekos\u0165 DB zn\u00ed\u017eila o 16% (o 4,3 GB v absol\u00fatnych \u010d\u00edslach) vyl\u00fa\u010den\u00edm null hodn\u00f4t z indexov. Obrovsk\u00e1 \u00faspora miesta na disku pri celkom jednoduch\u00fdch \u00faprav\u00e1ch. \ud83d\ude42 <\/p>\n
<\/p>\n
Probl\u00e9m \u0161iesty \u2013 absencia prim\u00e1rnych k\u013e\u00fa\u010dov<\/h3>\n
<\/p>\n
Z d\u00f4vodu \u0161pecif\u00edk mechanizmu MVCC v Postgres\u2019 e<\/a><\/noindex> m\u00f4\u017ee nasta\u0165 tak\u00e1 situ\u00e1cia, ako bloat<\/a><\/noindex>, ke\u010f sa ve\u013ekos\u0165 va\u0161ej tabu\u013eky r\u00fdchlo zvy\u0161uje v d\u00f4sledku ve\u013ek\u00e9ho mno\u017estva m\u0155tvych z\u00e1znamov. Naivne som si myslel, \u017ee sa n\u00e1s to net\u00fdka a \u017ee s na\u0161ou datab\u00e1zou sa to nestane, preto\u017ee sme, no \u00e1no!!!, norm\u00e1lni developeri\u2026 Ak\u00fd som bol hl\u00fapy a naivn\u00fd\u2026<\/p>\n
<\/p>\n
Jedn\u00e9ho kr\u00e1sneho d\u0148a ve\u013emi podaren\u00e1 migr\u00e1cia vzala a aktualizovala v\u0161etky z\u00e1znamy vo ve\u013ekej a akt\u00edvne pou\u017e\u00edvan\u00e9 tabu\u013eke. Z\u00edskali sme +100 GB na ve\u013ekosti tabu\u013eky z \u010dist\u00e9ho miesta. Bolo to prehnane frustruj\u00face, ale na\u0161e strasti na tom neskon\u010dili. Po 15 hodin\u00e1ch sa automatick\u00e1 \u00fadr\u017eba tejto tabu\u013eky skon\u010dila a bolo jasn\u00e9, \u017ee fyzick\u00e9 miesto sa nevr\u00e1ti. Nemohli sme zastavi\u0165 slu\u017ebu a vykona\u0165 VACUUM FULL, preto bolo prijat\u00e9 rozhodnutie pou\u017ei\u0165 pg_repack<\/a><\/noindex>. A tu sa uk\u00e1zalo, \u017ee pg_repack<\/em> nevie spracov\u00e1va\u0165 tabu\u013eky bez prim\u00e1rneho k\u013e\u00fa\u010da alebo in\u00e9ho obmedzenia jedine\u010dnosti, a na na\u0161ej tabu\u013eke prim\u00e1rny k\u013e\u00fa\u010d neexistoval. Tak vznikla diagnostika tables_without_primary_key<\/a><\/noindex>.<\/p>\n
<\/p>\n
Vo verzii kni\u017enice 0.1.5<\/strong> bola pridan\u00e1 mo\u017enos\u0165 zhroma\u017e\u010fova\u0165 \u00fadaje o bloat\u2019 e tabuliek a indexov a v\u010das na\u0148 reagova\u0165.<\/p>\n
<\/p>\n
Probl\u00e9my sedem a osem \u2013 nedostatok indexov a nevyu\u017eit\u00e9 indexy<\/h3>\n
<\/p>\n
Dve nasleduj\u00face diagnostiky \u2013 tables_with_missing_indexes<\/a><\/noindex> a unused_indexes<\/a><\/noindex> \u2013 v svojom kone\u010dnom znen\u00ed sa objavili relat\u00edvne ned\u00e1vno. Ide o to, \u017ee ich nebolo mo\u017en\u00e9 len tak jednoducho prida\u0165.<\/p>\n
<\/p>\n
Ako som u\u017e spomenul, pou\u017e\u00edvame konfigur\u00e1ciu s viacer\u00fdmi replikami a \u010d\u00edtac\u00ed n\u00e1por na r\u00f4znych hostite\u013eoch je z\u00e1sadne odli\u0161n\u00fd. Nakoniec vznik\u00e1 situ\u00e1cia, \u017ee niektor\u00e9 tabu\u013eky a indexy na niektor\u00fdch hostite\u013eoch sa takmer nepou\u017e\u00edvaj\u00fa, a na anal\u00fdzu je potrebn\u00e9 zhroma\u017e\u010fova\u0165 \u0161tatistiky zo v\u0161etk\u00fdch hostite\u013eov v clustri. Resetovanie \u0161tatist\u00edk<\/a><\/noindex> tie\u017e treba vykona\u0165 na ka\u017edom hostite\u013eovi v clustri, nemo\u017eno to urobi\u0165 len na majstrovi.<\/p>\n
<\/p>\n
Tento pr\u00edstup n\u00e1m umo\u017enil u\u0161etri\u0165 nieko\u013eko desiatok gigabajtov odstra\u0148ovan\u00edm indexov, ktor\u00e9 sa nikdy nepou\u017e\u00edvali, ako aj pridan\u00edm ch\u00fdbaj\u00facich indexov do zriedka pou\u017e\u00edvan\u00fdch tabuliek.<\/p>\n
<\/p>\n
Na z\u00e1ver<\/h3>\n
<\/p>\n
Samozrejme, pre v\u00e4\u010d\u0161inu diagnost\u00edk je mo\u017en\u00e9 nastavi\u0165 zoznam v\u00fdnimiek<\/a><\/noindex>. Takto je mo\u017en\u00e9 r\u00fdchlo zavies\u0165 kontroly vo va\u0161ej aplik\u00e1cii, zabr\u00e1ni\u0165 vzniku nov\u00fdch ch\u00fdb a potom postupne opravova\u0165 star\u00e9.<\/p>\n
<\/p>\n
Niektor\u00e9 diagnostiky m\u00f4\u017eu by\u0165 vykonan\u00e9 u\u017e vo funk\u010dn\u00fdch testoch hne\u010f po aplikovan\u00ed migr\u00e1ci\u00ed datab\u00e1zy. A toto je pravdepodobne jedna z najv\u00fdkonnej\u0161\u00edch funkci\u00ed mojej kni\u017enice. Pr\u00edklad pou\u017eitia si m\u00f4\u017eete pozrie\u0165 v demo<\/a><\/noindex>.<\/p>\n
<\/p>\n
Kontroly na nepou\u017e\u00edvan\u00e9 alebo ch\u00fdbaj\u00face indexy, ako aj na bloat, m\u00e1 zmysel vykon\u00e1va\u0165 iba na re\u00e1lnej datab\u00e1ze. Zozbieran\u00e9 hodnoty m\u00f4\u017eu by\u0165 zap\u00edsan\u00e9 do ClickHouse<\/a><\/noindex> alebo zaslan\u00e9 do monitorovacieho syst\u00e9mu.<\/p>\n
<\/p>\n
Ve\u013emi d\u00fafam, \u017ee pg-index-health<\/strong> bude u\u017eito\u010dn\u00e1 a vyh\u013ead\u00e1van\u00e1. M\u00f4\u017eete tie\u017e prispie\u0165 k rozvoju kni\u017enice ozn\u00e1men\u00edm o objaven\u00fdch probl\u00e9moch a navrhnut\u00edm nov\u00fdch diagnost\u00edk.<\/p>\n
Zdroj: habr.com<\/a> <\/p>","protected":false,"gt_translate_keys":[{"key":"rendered","format":"html"}]},"excerpt":{"rendered":"
\u041f\u0440\u0438\u0432\u0435\u0442. \u041c\u0435\u043d\u044f \u0437\u043e\u0432\u0443\u0442 \u0412\u0430\u043d\u044f, \u0438 \u044f Java-\u0440\u0430\u0437\u0440\u0430\u0431\u043e\u0442\u0447\u0438\u043a. \u0422\u0430\u043a \u043f\u043e\u043b\u0443\u0447\u0438\u043b\u043e\u0441\u044c, \u0447\u0442\u043e \u044f \u043c\u043d\u043e\u0433\u043e \u0440\u0430\u0431\u043e\u0442\u0430\u044e \u0441 PostgreSQL \u2013 \u0437\u0430\u043d\u0438\u043c\u0430\u044e\u0441\u044c \u043d\u0430\u0441\u0442\u0440\u043e\u0439\u043a\u043e\u0439 \u0411\u0414, \u043e\u043f\u0442\u0438\u043c\u0438\u0437\u0430\u0446\u0438\u0435\u0439 \u0441\u0442\u0440\u0443\u043a\u0442\u0443\u0440\u044b, \u043f\u0440\u043e\u0438\u0437\u0432\u043e\u0434\u0438\u0442\u0435\u043b\u044c\u043d\u043e\u0441\u0442\u044c\u044e \u0438 \u043d\u0435\u043c\u043d\u043e\u0433\u043e \u0438\u0433\u0440\u0430\u044e \u0432 DBA \u043f\u043e \u0432\u044b\u0445\u043e\u0434\u043d\u044b\u043c. \u0417\u0430 \u043f\u043e\u0441\u043b\u0435\u0434\u043d\u0435\u0435 \u0432\u0440\u0435\u043c\u044f \u044f \u043f\u0440\u0438\u0432\u0451\u043b \u0432 \u043f\u043e\u0440\u044f\u0434\u043e\u043a \u043d\u0435\u0441\u043a\u043e\u043b\u044c\u043a\u043e \u0431\u0430\u0437 \u0434\u0430\u043d\u043d\u044b\u0445 \u0432 \u043d\u0430\u0448\u0438\u0445 \u043c\u0438\u043a\u0440\u043e\u0441\u0435\u0440\u0432\u0438\u0441\u0430\u0445 \u0438 \u043d\u0430\u043f\u0438\u0441\u0430\u043b java-\u0431\u0438\u0431\u043b\u0438\u043e\u0442\u0435\u043a\u0443 pg-index-health, \u043a\u043e\u0442\u043e\u0440\u0430\u044f \u043e\u0431\u043b\u0435\u0433\u0447\u0430\u0435\u0442 \u044d\u0442\u0443 \u0440\u0430\u0431\u043e\u0442\u0443, \u044d\u043a\u043e\u043d\u043e\u043c\u0438\u0442 \u043c\u043e\u0451 \u0432\u0440\u0435\u043c\u044f \u0438 \u043f\u043e\u043c\u043e\u0433\u0430\u0435\u0442 […]<\/p>\n","protected":false,"gt_translate_keys":[{"key":"rendered","format":"html"}]},"author":1,"featured_media":72876,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[688],"tags":[],"class_list":["post-72875","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-administrirovanie"],"aioseo_notices":[],"aioseo_head":"\n\t\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\t\t\n\n","aioseo_head_json":{"title":"\ud83e\udd47Zdravie indexov v PostgreSQL o\u010dami Java v\u00fdvoj\u00e1ra | ProHoster","description":"Ahoj. Vol\u00e1m sa Vania a som Java v\u00fdvoj\u00e1r.","canonical_url":"https:\/\/prohoster.info\/sk\/blog\/administrirovanie\/zdorove-indeksov-v-postgresql-glazami-java-razrabotchika","robots":"max-image-preview:large","keywords":"","webmasterTools":{"miscellaneous":""},"schema":null,"og:locale":"sk_SK","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\u0417\u0434\u043e\u0440\u043e\u0432\u044c\u0435 \u0438\u043d\u0434\u0435\u043a\u0441\u043e\u0432 \u0432 PostgreSQL \u0433\u043b\u0430\u0437\u0430\u043c\u0438 Java-\u0440\u0430\u0437\u0440\u0430\u0431\u043e\u0442\u0447\u0438\u043a\u0430 | ProHoster","og:description":"\u041f\u0440\u0438\u0432\u0435\u0442. \u041c\u0435\u043d\u044f \u0437\u043e\u0432\u0443\u0442 \u0412\u0430\u043d\u044f, \u0438 \u044f Java-\u0440\u0430\u0437\u0440\u0430\u0431\u043e\u0442\u0447\u0438\u043a.","og:url":"https:\/\/prohoster.info\/sk\/blog\/administrirovanie\/zdorove-indeksov-v-postgresql-glazami-java-razrabotchika","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":"2020-03-05T05:42:09+00:00","article:modified_time":"2020-03-05T05:42:09+00:00","article:publisher":"https:\/\/www.facebook.com\/prohoster","article:author":"https:\/\/www.facebook.com\/prohoster"},"aioseo_meta_data":{"post_id":"72875","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":null,"breadcrumb_settings":null,"limit_modified_date":false,"reviewed_by":null,"ai":null,"created":"2021-02-28 18:43:29","updated":"2022-09-27 23:10:08","focus_keyword":null,"additional_keywords":null,"truseo_locale":null},"gt_translate_keys":[{"key":"link","format":"url"}],"_links":{"self":[{"href":"https:\/\/prohoster.info\/sk\/wp-json\/wp\/v2\/posts\/72875","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/prohoster.info\/sk\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/prohoster.info\/sk\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/prohoster.info\/sk\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/prohoster.info\/sk\/wp-json\/wp\/v2\/comments?post=72875"}],"version-history":[{"count":0,"href":"https:\/\/prohoster.info\/sk\/wp-json\/wp\/v2\/posts\/72875\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/prohoster.info\/sk\/wp-json\/wp\/v2\/media\/72876"}],"wp:attachment":[{"href":"https:\/\/prohoster.info\/sk\/wp-json\/wp\/v2\/media?parent=72875"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/prohoster.info\/sk\/wp-json\/wp\/v2\/categories?post=72875"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/prohoster.info\/sk\/wp-json\/wp\/v2\/tags?post=72875"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}