{"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\/hr\/blog\/administrirovanie\/zdorove-indeksov-v-postgresql-glazami-java-razrabotchika","title":{"rendered":"Zdravlje indeksa u PostgreSQL o\u010dima Java programera","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"<p>Bok.<\/p>\n<p><\/p>\n<p>Zovem se Vanya i ja sam Java programer. Radim puno s PostgreSQL-om \u2013 bavim se konfiguracijom baze podataka, optimizacijom strukture, performansi i pomalo igram DBA-a vikendom.<\/p>\n<p><\/p>\n<p>U posljednje vrijeme doveo sam u red nekoliko baza podataka u na\u0161im mikroservisima i napisao java biblioteku <noindex><a rel=\"nofollow\" href=\"https:\/\/github.com\/mfvanek\/pg-index-health\">pg-index-health<\/a><\/noindex>, koja olak\u0161ava taj posao, \u0161tedi moje vrijeme i poma\u017ee u izbjegavanju nekih uobi\u010dajenih gre\u0161aka koje programeri rade. O toj biblioteci \u0107u danas govoriti.<\/p>\n<p><\/p>\n<p><img decoding=\"async\" alt=\"Zdravlje indeksa u PostgreSQL o\u010dima Java programera\" src=\"\/wp-content\/uploads\/2020\/03\/e00bd48edf601f398bd7748754d48b80.jpg\" style=\"display:block;margin: 0 auto;\" \/><\/p>\n<p><\/p>\n<h3 id=\"disclaimer\">Odricanje<\/h3>\n<p><\/p>\n<p>Osnovna verzija PostgreSQL-a s kojom radim je verzija 10. Svi SQL upiti koje koristim tako\u0111er su testirani na verziji 11. Najmanje podr\u017eavana verzija je 9.6.<\/p>\n<p><\/p>\n<h3 id=\"predystoriya\">Povijest<\/h3>\n<p><\/p>\n<p>Sve je po\u010delo prije gotovo godinu dana s neobi\u010dnom situacijom za mene: konkurentno stvaranje indeksa na praznom mjestu zavr\u0161ilo je gre\u0161kom. Sam indeks, kao i obi\u010dno, ostao je u neva\u017ee\u0107em stanju u bazi. Analizom logova otkrio sam nedostatak <noindex><a rel=\"nofollow\" href=\"https:\/\/postgrespro.ru\/docs\/postgresql\/10\/runtime-config-resource\">temp_file_limit<\/a><\/noindex>. I tako je po\u010delo... Kopaju\u0107i dublje, otkrio sam mnogo problema u konfiguraciji baze podataka i, zasukav\u0161i rukave, s sjajem u o\u010dima krenuo ih popravljati.<\/p>\n<p><noindex><a rel=\"nofollow\" name=\"habracut\"><\/a><\/noindex><\/p>\n<h3 id=\"problema-pervaya--defoltnaya-konfiguraciya\">Problem prvi \u2013 zadana konfiguracija<\/h3>\n<p><\/p>\n<p>Mo\u017eda je metafora o Postgresu koji se mo\u017ee pokrenuti na aparatu za kavu svima ve\u0107 dosadila, ali... konfiguracija po defaultu doista postavlja neka pitanja. U najmanju ruku, treba obratiti pozornost na <strong>maintenance_work_mem<\/strong>, <strong>temp_file_limit<\/strong>, <strong>statement_timeout<\/strong> i <strong>lock_timeout<\/strong>.<\/p>\n<p><\/p>\n<p>U na\u0161em slu\u010daju <strong>maintenance_work_mem<\/strong> bio je po zadano 64 MB, a <strong>temp_file_limit<\/strong> oko 2 GB \u2013 jednostavno nam je manjkalo memorije za stvaranje indeksa na velikoj tablici.<\/p>\n<p><\/p>\n<p>Zato sam u <strong>pg-index-health<\/strong> skupio niz <noindex><a rel=\"nofollow\" href=\"https:\/\/github.com\/mfvanek\/pg-index-health\/blob\/dfbc7a37fc9c5f82957eeacdacd29a713fff7f51\/src\/main\/java\/io\/github\/mfvanek\/pg\/settings\/ImportantParam.java#L14\">klju\u010dnih<\/a><\/noindex>, po mom mi\u0161ljenju, parametara koje treba konfigurirati za svaku bazu podataka.<\/p>\n<p><\/p>\n<h3 id=\"problema-vtoraya--dubliruyuschiesya-indeksy\">Problem drugi \u2013 duplicirani indeksi<\/h3>\n<p><\/p>\n<p>Na\u0161e baze se nalaze na SSD diskovima, a koristimo <em>HA<\/em>-konfiguraciju s vi\u0161e podatkovnih centara, master hostom i <em>n<\/em>-nim brojem replikacija. Mjesto na disku je za nas jako dragocjen resurs; jednako je va\u017eno kao i performanse i potro\u0161nja CPU-a. Stoga, s jedne strane, potrebni su nam indeksi za brzo \u010ditanje, a s druge strane, ne \u017eelimo vidjeti u bazi suvi\u0161ne indekse, jer oni tro\u0161e prostor i usporavaju a\u017euriranje podataka.<\/p>\n<p><\/p>\n<p>I tako, nakon \u0161to smo obnovili sve <noindex><a rel=\"nofollow\" href=\"https:\/\/github.com\/mfvanek\/pg-index-health\/blob\/master\/src\/main\/resources\/sql\/invalid_indexes.sql\">neva\u017ee\u0107e indekse<\/a><\/noindex> i pregledali <noindex><a rel=\"nofollow\" href=\"https:\/\/www.youtube.com\/watch?v=aaecM4wKdhY\">prezentacije Olega Bartunova<\/a><\/noindex>, odlu\u010dio sam provesti \u201eveliko\u201c \u010di\u0161\u0107enje. Ispostavilo se da programeri ne vole \u010ditati dokumentaciju baze podataka. Jako ne vole. Zbog toga se javljaju dvije uobi\u010dajene gre\u0161ke \u2013 ru\u010dno stvoren indeks na primarni klju\u010d i sli\u010dan \u201eru\u010dni\u201c indeks na jedinstveni stupac. Rije\u010d je o tome da nisu potrebni \u2013 Postgres \u0107e sve u\u010diniti sam. Takve indekse mo\u017eete slobodno ukloniti, a za to postoji dijagnostika <noindex><a rel=\"nofollow\" href=\"https:\/\/github.com\/mfvanek\/pg-index-health\/blob\/master\/src\/main\/resources\/sql\/duplicated_indexes.sql\">duplicirani_indeksi<\/a><\/noindex>.<\/p>\n<p><\/p>\n<h3 id=\"problema-tretya--peresekayuschiesya-indeksy\">Tre\u0107i problem \u2013 preklapaju\u0107i indeksi<\/h3>\n<p><\/p>\n<p>Ve\u0107ina po\u010detnika programera stvara indekse na jedan stupac. Postupno, kako postaju sigurniji, ljudi po\u010dinju optimizirati svoje upite i dodavati slo\u017eenije indekse koji uklju\u010duju vi\u0161e stupaca. Tako nastaju indeksi na stupcima <em>A<\/em>, <em>A+B<\/em>, <em>A+B+C<\/em> itd. Prva dva od ovih indeksa mo\u017eete slobodno izbaciti, jer su prefiksi tre\u0107eg. To tako\u0111er zna\u010dajno \u0161tedi prostor na disku i za to postoji dijagnostika <noindex><a rel=\"nofollow\" href=\"https:\/\/github.com\/mfvanek\/pg-index-health\/blob\/master\/src\/main\/resources\/sql\/intersected_indexes.sql\">preklapaju\u0107i_indeksi<\/a><\/noindex>.<\/p>\n<p><\/p>\n<h3 id=\"problema-chetvertaya--vneshnie-klyuchi-bez-indeksov\">\u010cetvrti problem \u2013 vanjski klju\u010devi bez indeksa<\/h3>\n<p><\/p>\n<p>Postgres dopu\u0161ta stvaranje ograni\u010denja vanjskog klju\u010da bez navo\u0111enja prate\u0107eg indeksa. U mnogim situacijama to nije problem i mo\u017ee se \u010dak ni ne manifestirati\u2026 Do odre\u0111enog trenutka\u2026<\/p>\n<p><\/p>\n<p>Tako je bilo i kod nas: jednostavno je u nekom trenutku, job koji se izvr\u0161avao prema rasporedu i \u010di\u0161\u0107enje baze od testnih narud\u017ebi, po\u010deo \u201cslagati\u201d na\u0161eg glavnog hosta. CPU i IO su se naglo pove\u0107ali, upiti su usporili i prekidali zbog vremenskog limita, servis se sru\u0161io. Brza analiza <noindex><a rel=\"nofollow\" href=\"https:\/\/postgrespro.ru\/docs\/postgresql\/10\/monitoring-stats\">pg_stat_activity<\/a><\/noindex> pokazala je da su se zapeli upiti tipa:<\/p>\n<p><\/p>\n<pre><code class=\"sql\">obri&scaron;i iz &lt;table&gt; gdje je id u (&hellip;)<\/code><\/pre>\n<p><\/p>\n<p>Pri tome je indeks po id-u u ciljnoj tablici, naravno, bio, a zapisi su se brisali prema uvjetu u vrlo malom broju. \u010cinilo se da sve treba raditi, ali, na\u017ealost, nije radilo.<\/p>\n<p><\/p>\n<p>U pomo\u0107 je do\u0161la \u010darobna <strong>explain analyze<\/strong> i objasnila da osim brisanja zapisa u ciljnoj tablici, jo\u0161 se vr\u0161i provjera referentne cjelovitosti, i u jednoj od povezanih tablica ta provjera ide u <em>sekvencijalno pretra\u017eivanje<\/em> zbog nedostatka odgovaraju\u0107eg indeksa. Tako je nastala dijagnostika <noindex><a rel=\"nofollow\" href=\"https:\/\/github.com\/mfvanek\/pg-index-health\/blob\/master\/src\/main\/resources\/sql\/foreign_keys_without_index.sql\">vanjski_klju\u010devi_bez_indeksa<\/a><\/noindex>.<\/p>\n<p><\/p>\n<h3 id=\"problema-pyataya--null-value-v-indeksah\">Peti problem \u2013 null vrijednost u indeksima<\/h3>\n<p><\/p>\n<p>Zadano, Postgres uklju\u010duje null vrijednosti u btree-indekse, ali su obi\u010dno nepotrebne. Stoga se trudim da ovakve null vrijednosti uklonim (dijagnostika <noindex><a rel=\"nofollow\" href=\"https:\/\/github.com\/mfvanek\/pg-index-health\/blob\/master\/src\/main\/resources\/sql\/indexes_with_null_values.sql\">indeksi_s_null_vrijednostima<\/a><\/noindex>), stvaraju\u0107i parcijalne indekse na nullable-stupce poput <code>gdje <A> nije null<\/code>. Na taj na\u010din uspjeli smo smanjiti veli\u010dinu jednog od na\u0161ih indeksa s 1877 MB na 16 KB. A u jednoj od usluga, ukupna veli\u010dina baze podataka smanjena je za 16% (za 4,3 GB u apsolutnim brojkama) isklju\u010divanjem null vrijednosti iz indeksa. Ogromna u\u0161teda prostora na disku uz prili\u010dno jednostavne izmjene. \ud83d\ude42 <\/p>\n<p><\/p>\n<h3 id=\"problema-shestaya--otsutstvie-pervichnyh-klyuchey\">\u0160esti problem \u2013 nedostatak primarnih klju\u010deva<\/h3>\n<p><\/p>\n<p>Zbog osobitosti mehanizma <noindex><a rel=\"nofollow\" href=\"https:\/\/habr.com\/ru\/company\/postgrespro\/blog\/442804\/\">MVCC u Postgresu<\/a><\/noindex> mogu\u0107a je situacija kada <noindex><a rel=\"nofollow\" href=\"https:\/\/habr.com\/ru\/post\/169939\/\">bloat<\/a><\/noindex>se veli\u010dina va\u0161e tablice brzo pove\u0107ava zbog velikog broja mrtvih zapisa. Naivno sam vjerovao da nam to ne prijeti, i da se s na\u0161om bazom to ne\u0107e dogoditi, jer smo, oho-ho!!!, normalni programeri\u2026 Kako sam bio glup i naivan\u2026<\/p>\n<p><\/p>\n<p>Jednog divnog dana jedna \u010dudesna migracija je a\u017eurirala sve zapise u velikoj i aktivno kori\u0161tenoj tablici. Dobili smo +100 GB dodatne veli\u010dine tablice iz ni\u010dega. Bilo je nevjerojatno frustriraju\u0107e, ali na\u0161e nevolje tu nisu stale. Nakon \u0161to je nakon 15 sati zavr\u0161ila autovacuum na ovoj tablici, postalo je jasno da se fizi\u010dko mjesto ne\u0107e vratiti. Nismo mogli zaustaviti servis i napraviti VACUUM FULL, pa je donesena odluka da se koristi <noindex><a rel=\"nofollow\" href=\"https:\/\/github.com\/reorg\/pg_repack\">pg_repack<\/a><\/noindex>. I tu se pokazalo da <em>pg_repack<\/em> ne mo\u017ee obraditi tablice bez primarnog klju\u010da ili drugog ograni\u010denja jedinstvenosti, a u na\u0161oj tablici nije bilo primarnog klju\u010da. Tako je nastala dijagnostika <noindex><a rel=\"nofollow\" href=\"https:\/\/github.com\/mfvanek\/pg-index-health\/blob\/master\/src\/main\/resources\/sql\/tables_without_primary_key.sql\">tables_without_primary_key<\/a><\/noindex>.<\/p>\n<p><\/p>\n<p>U verziji biblioteke <strong>0.1.5<\/strong> dodana je mogu\u0107nost prikupljanja podataka o bloat-u tablica i indeksa i pravovremenog reagiranja na njega.<\/p>\n<p><\/p>\n<h3 id=\"problemy-sem-i-vosem--nehvatka-indeksov-i-neispolzuemye-indeksy\">Problemi sedam i osam \u2013 nedostatak indeksa i neiskori\u0161teni indeksi<\/h3>\n<p><\/p>\n<p>Dva sljede\u0107a dijagnosti\u010dka alata \u2014 <noindex><a rel=\"nofollow\" href=\"https:\/\/github.com\/mfvanek\/pg-index-health\/blob\/master\/src\/main\/resources\/sql\/tables_with_missing_indexes.sql\">tables_with_missing_indexes<\/a><\/noindex> i <noindex><a rel=\"nofollow\" href=\"https:\/\/github.com\/mfvanek\/pg-index-health\/blob\/master\/src\/main\/resources\/sql\/unused_indexes.sql\">unused_indexes<\/a><\/noindex> \u2013 u svom kona\u010dnom obliku pojavili su se relativno nedavno. I stvar je u tome da ih nije bilo mogu\u0107e jednostavno dodati.<\/p>\n<p><\/p>\n<p>Kao \u0161to sam ve\u0107 spomenuo, koristimo konfiguraciju s vi\u0161e replika, a \u010ditateljski optere\u0107enje na razli\u010ditim hostovima je principijelno razli\u010dito. Na kraju se stvara situacija da neke tablice i indeksi na nekim hostovima prakti\u010dki nisu kori\u0161teni, a za analizu je potrebno prikupljati statistiku sa svih hostova u klasteru. <noindex><a rel=\"nofollow\" href=\"https:\/\/github.com\/mfvanek\/pg-index-health\/blob\/dfbc7a37fc9c5f82957eeacdacd29a713fff7f51\/src\/main\/java\/io\/github\/mfvanek\/pg\/index\/health\/IndexesHealth.java#L165\">Resetiranje statistike<\/a><\/noindex> tako\u0111er treba biti u\u010dinjeno na svakom hostu u klasteru, ne mo\u017ee se napraviti samo na glavnom.<\/p>\n<p><\/p>\n<p>Ovaj pristup nam je omogu\u0107io da u\u0161tedimo nekoliko desetaka gigabajta brisanjem indeksa koji nikada nisu kori\u0161\u0107eni, a tako\u0111e da dodamo nedostaju\u0107e indekse na retko kori\u0161\u0107ene tabele.<\/p>\n<p><\/p>\n<h3 id=\"v-kachestve-zaklyucheniya\">Kao zaklju\u010dak<\/h3>\n<p><\/p>\n<p>Naravno, prakti\u010dno za sve dijagnostike mogu se postaviti <noindex><a rel=\"nofollow\" href=\"https:\/\/github.com\/mfvanek\/pg-index-health\/blob\/dfbc7a37fc9c5f82957eeacdacd29a713fff7f51\/src\/main\/java\/io\/github\/mfvanek\/pg\/index\/health\/logger\/Exclusions.java#L26\">lista izuzetaka<\/a><\/noindex>. Na taj na\u010din mo\u017eete brzo implementirati provere u va\u0161oj aplikaciji, spre\u010davaju\u0107i pojavu novih gre\u0161aka, a zatim postepeno ispravljati stare.<\/p>\n<p><\/p>\n<p>Deo dijagnostika mo\u017ee se izvoditi ve\u0107 u funkcionalnim testovima odmah nakon uvo\u0111enja migracija baze podataka. I to je, verovatno, jedna od najmo\u0107nijih mogu\u0107nosti moje biblioteke. Primer kori\u0161\u0107enja mo\u017eete pogledati u <noindex><a rel=\"nofollow\" href=\"https:\/\/github.com\/mfvanek\/pg-index-health-demo\/blob\/master\/src\/test\/java\/io\/github\/mfvanek\/pg\/index\/health\/demo\/IndexesMaintenanceTest.java\">demo<\/a><\/noindex>.<\/p>\n<p><\/p>\n<p>Provere neupotrebljenih ili nedostaju\u0107ih indeksa, kao i onih koje su ote\u017eane (bloat), ima smisla izvoditi samo na pravoj bazi podataka. Sakupljene vrednosti mogu se zabele\u017eiti u <noindex><a rel=\"nofollow\" href=\"https:\/\/github.com\/ClickHouse\/ClickHouse\">ClickHouse<\/a><\/noindex> ili poslati u sistem za monitoring.<\/p>\n<p><\/p>\n<p>Zaista se nadam da <strong>pg-index-health<\/strong> \u0107e biti korisna i tra\u017eena. Tako\u0111e mo\u017eete pomo\u0107i razvoju biblioteke tako \u0161to \u0107ete prijaviti otkrivene probleme i predlo\u017eiti nove dijagnostike.<\/p>\n<p>Izvor: <a content=\"nofollow\" rel=\"nofollow\" href=\"https:\/\/habr.com\/ru\/post\/490824\/\">habr.com<\/a> <\/p>","protected":false,"gt_translate_keys":[{"key":"rendered","format":"html"}]},"excerpt":{"rendered":"<p>\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 [&hellip;]<\/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<!-- All in One SEO 5.0.5.1 - aioseo.com -->\n\t<meta name=\"description\" content=\"\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.\" \/>\n\t<meta name=\"robots\" content=\"max-image-preview:large\" \/>\n\t<meta name=\"author\" content=\"Yuri Gagarin\"\/>\n\t<link rel=\"canonical\" href=\"https:\/\/prohoster.info\/hr\/blog\/administrirovanie\/zdorove-indeksov-v-postgresql-glazami-java-razrabotchika\" \/>\n\t\t<meta name=\"generator\" content=\"All in One SEO (AIOSEO) 5.0.5.1\" \/>\n\t\t<meta property=\"og:locale\" content=\"hr_HR\" \/>\n\t\t<meta property=\"og:site_name\" content=\"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\" \/>\n\t\t<meta property=\"og:type\" content=\"article\" \/>\n\t\t<meta property=\"og:title\" content=\"\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\" \/>\n\t\t<meta property=\"og:description\" content=\"\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.\" \/>\n\t\t<meta property=\"og:url\" content=\"https:\/\/prohoster.info\/hr\/blog\/administrirovanie\/zdorove-indeksov-v-postgresql-glazami-java-razrabotchika\" \/>\n\t\t<meta property=\"og:image\" content=\"https:\/\/prohoster.info\/wp-content\/uploads\/2021\/11\/logo-350.jpg\" \/>\n\t\t<meta property=\"og:image:secure_url\" content=\"https:\/\/prohoster.info\/wp-content\/uploads\/2021\/11\/logo-350.jpg\" \/>\n\t\t<meta property=\"og:image:width\" content=\"350\" \/>\n\t\t<meta property=\"og:image:height\" content=\"350\" \/>\n\t\t<meta property=\"article:published_time\" content=\"2020-03-05T05:42:09+00:00\" \/>\n\t\t<meta property=\"article:modified_time\" content=\"2020-03-05T05:42:09+00:00\" \/>\n\t\t<meta property=\"article:publisher\" content=\"https:\/\/www.facebook.com\/prohoster\" \/>\n\t\t<meta property=\"article:author\" content=\"https:\/\/www.facebook.com\/prohoster\" \/>\n\t\t<!-- All in One SEO -->\n\n","aioseo_head_json":{"title":"\ud83e\udd47Zdravlje indeksa u PostgreSQL o\u010dima Java programera | ProHoster","description":"Zdravo. Zovem se Vanja i ja sam Java programer.","canonical_url":"https:\/\/prohoster.info\/hr\/blog\/administrirovanie\/zdorove-indeksov-v-postgresql-glazami-java-razrabotchika","robots":"max-image-preview:large","keywords":"","webmasterTools":{"miscellaneous":""},"schema":null,"og:locale":"hr_HR","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\/hr\/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\/hr\/wp-json\/wp\/v2\/posts\/72875","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/prohoster.info\/hr\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/prohoster.info\/hr\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/prohoster.info\/hr\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/prohoster.info\/hr\/wp-json\/wp\/v2\/comments?post=72875"}],"version-history":[{"count":0,"href":"https:\/\/prohoster.info\/hr\/wp-json\/wp\/v2\/posts\/72875\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/prohoster.info\/hr\/wp-json\/wp\/v2\/media\/72876"}],"wp:attachment":[{"href":"https:\/\/prohoster.info\/hr\/wp-json\/wp\/v2\/media?parent=72875"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/prohoster.info\/hr\/wp-json\/wp\/v2\/categories?post=72875"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/prohoster.info\/hr\/wp-json\/wp\/v2\/tags?post=72875"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}