{"id":52584,"date":"2019-11-12T00:00:00","date_gmt":"2019-11-11T21:00:00","guid":{"rendered":"https:\/\/prohoster.info\/blog\/blog_prohoster\/zamena-eav-na-jsonb-v-postgresql"},"modified":"2020-02-18T14:00:21","modified_gmt":"2020-02-18T11:00:21","slug":"zamena-eav-na-jsonb-v-postgresql","status":"publish","type":"post","link":"https:\/\/prohoster.info\/bs\/blog\/administrirovanie\/zamena-eav-na-jsonb-v-postgresql","title":{"rendered":"Zamjena EAV s JSONB u PostgreSQL","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"<blockquote><p>TL; DR: JSONB mo\u017ee zna\u010dajno olak\u0161ati razvoj Baza podataka bez \u017ertvovanja performansi u upitima.<\/p><\/blockquote>\n<p><\/p>\n<h3>Uvod<\/h3>\n<p>\nUzmimo klasi\u010dan primjer, vjerovatno jedan od najstarijih na\u010dina kori\u0161tenja u svijetu relacijskih baza podataka (baza podataka): imamo entitet i treba da sa\u010duvamo odre\u0111ena svojstva (atribute) tog entiteta. Me\u0111utim, ne svi primeri moraju imati isti skup svojstava, a i u budu\u0107nosti je mogu\u0107e dodavanje novih svojstava.<\/p>\n<p>Najjednostavniji na\u010din rje\u0161avanja ovog problema je stvaranje kolone u tabeli baze podataka za svaku vrijednost svojstva i jednostavno popunjavanje onih koje su potrebne za odre\u0111eni primjer entiteta. Odli\u010dno! Problem je re\u0161en\u2026 do trenutka kada va\u0161a tabela ne sadr\u017ei milione zapisa i kada ne do\u0111e do potrebe za dodavanjem nove stavke.<\/p>\n<p>Razmotrimo EAV obrazac (<noindex><a rel=\"nofollow\" href=\"https:\/\/en.wikipedia.org\/wiki\/Entity%E2%80%93attribute%E2%80%93value_model\">Entity-Attribute-Value<\/a><\/noindex>), on se dovoljno \u010desto pojavljuje. Jedna tabela sadr\u017ei entitete (zapise), druga tabela sadr\u017ei imena svojstava (atributa), a tre\u0107a tabela povezuje entitete s njihovim atributima i sadr\u017ei vrijednosti tih atributa za trenutni entitet. Ovo vam omogu\u0107ava da imate razli\u010dite skupove svojstava za razli\u010dite objekte, kao i da dodajete svojstva \"u hodu\", ne mijenjaju\u0107i strukturu baze podataka.<br \/>\n<noindex><a rel=\"nofollow\" name=\"habracut\"><\/a><\/noindex><br \/>\nIpak, ne bih pisao ovu bele\u0161ku da nije bilo nedostataka u pristupu kori\u0161\u0107enju EVA. Naime, da bi se dobila jedna ili vi\u0161e entiteta koji imaju po jedan atribut, potrebna su 2 spajanja (join) u upitu: prvo \u2013 spajanje sa tabelom atributa, a drugo \u2013 spajanje sa tabelom vrednosti. Ako entitet ima 2 atributa, potrebno je ve\u0107 4 spajanja! Pored toga, svi atributi se obi\u010dno \u010duvaju u obliku stringova, \u0161to dovodi do konverzije tipova, kako za rezultat, tako i za uslov WHERE. Ako pi\u0161ete mnogo upita, to je dovoljno rasipno, s aspekta kori\u0161\u0107enja resursa.<\/p>\n<p>Uprkos ovim o\u010diglednim nedostacima, EAV se ve\u0107 dugo koristi za rje\u0161avanje ovakvih problema. To su bila neizbje\u017ena ograni\u010denja, a bolje alternative jednostavno nije bilo. <br \/>\nAli tada je u PostgreSQL-u pojavila nova \"tehnologija\"\u2026<\/p>\n<p>Po\u010dinjaju\u0107i od PostgreSQL 9.4, tip podataka JSONB je dodat za skladi\u0161tenje binarnih JSON podataka. Iako skladi\u0161tenje JSON-a u ovom formatu obi\u010dno zahteva malo vi\u0161e prostora i vremena od prostog tekstualnog JSON-a, operacije nad njim se obavljaju znatno br\u017ee. Tako\u0111e, JSONB podr\u017eava indeksiranje, \u0161to \u010dini upite jo\u0161 br\u017eim.<\/p>\n<p>Tip podataka JSONB omogu\u0107ava nam da zamenimo slo\u017eeni EAV obrazac jednostavnim dodavanjem jednog JSONB stupca u na\u0161u tabelu entiteta, \u0161to zna\u010dajno pojednostavljuje dizajn baze podataka. Me\u0111utim, mnogi tvrde da bi to trebalo pratiti smanjenjem performansi\u2026 Zbog ovog razloga je ovaj \u010dlanak i napisan.<\/p>\n<h3>Pode\u0161avanje testne baze podataka<\/h3>\n<p>\nZa ovu poredbe sam kreirao bazu podataka na novoj instalaciji PostgreSQL 9.5 na 80-dolarskoj konfiguraciji. <noindex><a rel=\"nofollow\" href=\"https:\/\/www.digitalocean.com\/\">DigitalOcean<\/a><\/noindex> Ubuntu 14.04. Nakon \u0161to sam pode\u0161avao neke parametre u postgresql.conf, pokrenuo sam <noindex><a rel=\"nofollow\" href=\"https:\/\/gist.github.com\/coussej\/80c385332ce37df6687f\">ovaj<\/a><\/noindex> script putem psql-a. Za predstavljanje podataka u obliku EAV kreirane su slede\u0107e tabele:<\/p>\n<pre><code class=\"pgsql\">CREATE TABLE entity ( \n  id           SERIAL PRIMARY KEY, \n  name         TEXT, \n  description  TEXT\n);\nCREATE TABLE entity_attribute (\n  id          SERIAL PRIMARY KEY, \n  name        TEXT\n);\nCREATE TABLE entity_attribute_value (\n  id                  SERIAL PRIMARY KEY, \n  entity_id           INT    REFERENCES entity(id), \n  entity_attribute_id INT    REFERENCES entity_attribute(id), \n  value               TEXT\n);\n<\/code><\/pre>\n<p>\nIspod je tabela u kojoj \u0107e se \u010duvati isti podaci, ali sa atributima u stupcu tipa JSONB \u2013 <i>properties<\/i>.<\/p>\n<pre><code class=\"pgsql\">CREATE TABLE entity_jsonb (\n  id          SERIAL PRIMARY KEY, \n  name        TEXT, \n  description TEXT,\n  properties  JSONB\n);\n<\/code><\/pre>\n<p>\nIzgleda mnogo jednostavnije, zar ne? Zatim je u tabelama entiteta (<i>entity<\/i> &amp; <i>entity_jsonb<\/i>) dodano 10 miliona zapisa, i samim tim su popunjeni isti podaci u tabelama gde se koristi EAV obrazac i pristup sa JSONB stupcem \u2013 <i>entity_jsonb.properties<\/i>. Tako smo dobili nekoliko razli\u010ditih tipova podataka me\u0111u celokupnim skupom svojstava. Primer podataka:<\/p>\n<pre><code class=\"json\">{\n  id:          1\n  name:        \"Entity1\"\n  description: \"Test entitet br. 1\"\n  properties:  {\n    color:        \"red\"\n    lenght:       120\n    width:        3.1882420\n    hassomething: true\n    country:      \"Belgija\"\n  } \n}<\/code><\/pre>\n<p>\nDakle, sada imamo iste podatke za dva varijante. Po\u010dnimo sa upore\u0111ivanjem implementacija u radu!<\/p>\n<h3>Pojednostavljenje dizajna<\/h3>\n<p>\nVe\u0107 je re\u010deno da je dizajn baze podataka zna\u010dajno pojednostavljen: jedna tabela, kori\u0161\u0107enjem JSONB stupca za svojstva, umesto kori\u0161\u0107enja tri tabele za EAV. Kako se to odra\u017eava na upitima? A\u017euriranje jednog svojstva entiteta izgleda ovako:<\/p>\n<pre><code class=\"pgsql\">-- EAV\nUPDATE entity_attribute_value \nSET value = 'blue' \nWHERE entity_attribute_id = 1 \n  AND entity_id = 120;\n\n-- JSONB\nUPDATE entity_jsonb \nSET properties = jsonb_set(properties, '{\"color\"}', '\"blue\"') \nWHERE id = 120;\n<\/code><\/pre>\n<p>\nKao \u0161to vidimo, poslednji upit ne izgleda jednostavnije. Da bismo a\u017eurirali vrednost atributa u JSONB objektu, moramo koristiti funkciju <noindex><a rel=\"nofollow\" href=\"http:\/\/www.postgresql.org\/docs\/9.5\/static\/functions-json.html\">jsonb_set()<\/a><\/noindex>, i moramo proslediti novu vrednost kao JSONB objekat. Ipak, ne trebamo unapred znati bilo koji identifikator. Gledaju\u0107i primer sa EAV, potrebno je znati i entity_id i entity_attribute_id da bismo izvr\u0161ili a\u017euriranje. Ako \u017eelite da a\u017eurirate atribut u JSONB koloni prema imenu objekta, \u2013 to se mo\u017ee uraditi u jednoj jednostavnoj liniji.<\/p>\n<p>Sada hajde da izaberemo entitet koji smo upravo a\u017eurirali na osnovu njegovog novog kolor:<\/p>\n<pre><code class=\"pgsql\">-- EAV\nSELECT e.name \nFROM entity e \n  INNER JOIN entity_attribute_value eav ON e.id = eav.entity_id\n  INNER JOIN entity_attribute ea ON eav.entity_attribute_id = ea.id\nWHERE ea.name = 'color' AND eav.value = 'blue';\n\n-- JSONB\nSELECT name \nFROM entity_jsonb \nWHERE properties -&gt;&gt; 'color' = 'blue';\n<\/code><\/pre>\n<p>\nMislim da se mo\u017eemo slo\u017eiti da je drugi upit kra\u0107i (bez join!), i prema tome \u010ditljiviji. Ovde pobedjuje JSONB! Koristimo JSON operator -&gt;&gt; kako bismo dobili boju kao tekstualnu vrednost iz JSONB objekta. Postoji i drugi na\u010din da se postigne isti rezultat u JSONB modelu koriste\u0107i operator @&gt;:<\/p>\n<pre><code class=\"pgsql\">-- JSONB \nSELECT name \nFROM entity_jsonb \nWHERE properties @&gt; '{\"color\": \"blue\"}';\n<\/code><\/pre>\n<p>\nOvo je malo slo\u017eenije: proveravamo da li JSON objekat u koloni svojstava sadr\u017ei objekat koji se nalazi desno od operatora @&gt;. Manje \u010ditljivo, ali efikasnije (vidi dalje). <\/p>\n<p>Pojednostavimo upotrebu JSONB jo\u0161 vi\u0161e kada vam je potrebno da izaberete vi\u0161e svojstava odjednom. Tu JSONB pristup zapravo dolazi do izra\u017eaja: jednostavno biramo svojstva kao dodatne kolone u na\u0161em skupu rezultata bez potrebe za spajanjima:<\/p>\n<pre><code class=\"pgsql\">-- JSONB \nSELECT name\n  , properties -&gt;&gt; 'color'\n  , properties -&gt;&gt; 'country'\nFROM entity_jsonb \nWHERE id = 120;\n<\/code><\/pre>\n<p>\nSa EAV bi\u0107e vam potrebna 2 spajanja za svako svojstvo koje \u017eelite da upitate. Po mom mi\u0161ljenju, navedeni upiti pokazuju zna\u010dajno pojednostavljenje u dizajnu baze podataka. Vi\u0161e primera kako pisati upite za JSONB mo\u017eete tako\u0111e na\u0107i u <noindex><a rel=\"nofollow\" href=\"http:\/\/schinckel.net\/2014\/05\/25\/querying-json-in-postgres\/\">ovom<\/a><\/noindex> postu.<br \/>\nSada je do\u0161lo vreme da razgovaramo o performansama.<\/p>\n<h3>Performanse<\/h3>\n<p>\nDa bih uporedio performanse, koristio sam <noindex><a rel=\"nofollow\" href=\"http:\/\/www.postgresql.org\/docs\/9.1\/static\/sql-explain.html\">EXPLAIN ANALYZE<\/a><\/noindex> u upitima, za mjerenje vremena izvr\u0161avanja. Svaki upit je izvr\u0161en najmanje tri puta, jer prvom izvr\u0161avanju planeru upita treba vi\u0161e vremena. Prvo sam izvr\u0161io upite bez ikakvih indeksa. O\u010digledno, to je pru\u017eilo prednost JSONB-u, jer spojevi potrebni za EAV nisu mogli koristiti indekse (polja stranih klju\u010deva nisu bila indeksirana). Nakon toga sam stvorio indeks za 2 kolone stranih klju\u010deva u EAV tabeli, kao i indeks <noindex><a rel=\"nofollow\" href=\"http:\/\/www.postgresql.org\/docs\/9.1\/static\/textsearch-indexes.html\">GIN<\/a><\/noindex> za kolonu JSONB.<\/p>\n<p>A\u017euriranja podataka pokazala su sljede\u0107e rezultate po vremenu (u ms). Imajte na umu da je skala logaritamska:<\/p>\n<p><img decoding=\"async\" alt=\"Zamjena EAV s JSONB u PostgreSQL\" src=\"\/wp-content\/uploads\/2019\/11\/8a12ccd7a46d04868b1cc5fcaf01a581.jpg\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<br \/>\nVidimo da je JSONB mnogo (&gt; 50000-x) br\u017ei od EAV-a kada se ne koriste indeksi, zbog razloga navedenog iznad. Kada indeksiramo kolone sa primarnim klju\u010devima, razlika gotovo nestaje, ali je JSONB jo\u0161 uvek 1,3 puta br\u017ei od EAV-a. Imajte na umu da indeks u koloni JSONB ovde ne uti\u010de, jer ne koristimo kolonu svojstava u kriterijumima ocenjivanja. <\/p>\n<p>Za odabir podataka na temelju vrednosti svojstva dobijamo sljede\u0107e rezultate (obi\u010dna skala):<\/p>\n<p><img decoding=\"async\" alt=\"Zamjena EAV s JSONB u PostgreSQL\" src=\"\/wp-content\/uploads\/2019\/11\/e9a1fd797ef60132e661da686f6214a3.jpg\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<br \/>\nMo\u017ee se primijetiti da JSONB opet radi br\u017ee od EAV-a bez indeksa, ali kada EAV ima indekse \u2013 jo\u0161 uvek radi br\u017ee od JSONB-a. Me\u0111utim, tada sam primetio da je vreme za JSONB upite bilo isto, \u0161to me navelo na zaklju\u010dak da GIN indeks ne funkcioni\u0161e. Naime, kada koristite GIN indeks za kolonu sa popunjenim svojstvima, on deluje samo kada koristite operator uklju\u010divanja @&gt;. Koristio sam ovo u novom testu, \u0161to je imalo ogroman uticaj na vreme: samo 0,153 ms! To je 15000 puta br\u017ee od EAV-a i 25000 puta br\u017ee od operatora -&gt;&gt;. <\/p>\n<p>Mislim da je to bilo dovoljno brzo!<\/p>\n<h3>Veli\u010dina tabela Baze Podataka<\/h3>\n<p>\nPore\u0111imo veli\u010dine tabela kod oba pristupa. U psql-u mo\u017eemo prikazati veli\u010dinu svih tabela i indeksa koriste\u0107i komandu <b>dti+<\/b><\/p>\n<p><img decoding=\"async\" alt=\"Zamjena EAV s JSONB u PostgreSQL\" src=\"\/wp-content\/uploads\/2019\/11\/c6c1fe7901fe9ae2bd446cf4ae99b923.jpg\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<br \/>\nZa pristup EAV, veli\u010dine tabela su oko 3068 MB, a indeksi do 3427 MB, \u0161to ukupno daje 6,43 GB. Kada koristimo pristup sa JSONB-om, koristi se 1817 MB za tabelu i 318 MB za indekse, \u0161to \u010dini 2,08 GB. To je tri puta manje! Ova \u010dinjenica me malo iznenadila, jer \u010duvamo imena svojstava u svakom JSONB objektu. <\/p>\n<p>Me\u0111utim, brojke same govore za sebe: u EAV-u \u010duvamo 2 cjelobrojna vanjska klju\u010da za vrijednost atributa, \u0161to rezultira dodatnih 8 bajtova podataka. Osim toga, u EAV-u se sve vrijednosti svojstava \u010duvaju kao tekst, dok JSONB koristi numeri\u010dke i logi\u010dke vrijednosti gdje je to mogu\u0107e, \u0161to rezultira manjim obimom.<\/p>\n<h3>Zaklju\u010dci<\/h3>\n<p>\nU cjelini, mislim da \u010duvanje svojstava entiteta u formatu JSONB mo\u017ee znatno pojednostaviti dizajn i odr\u017eavanje va\u0161e baze podataka. Ako izvodite mnogo upita, sve \u0161to se \u010duva u jednoj tabeli sa entitetom zaista \u0107e raditi efikasnije. A to \u0161to to pojednostavljuje interakciju izme\u0111u podataka ve\u0107 je plus, ali i rezultat je baza podataka tri puta manja po obimu.<\/p>\n<p>Tako\u0111er, prema provedenim testovima, mo\u017ee se zaklju\u010diti da su gubici u performansama vrlo neznatni. U nekim slu\u010dajevima, JSONB \u010dak radi br\u017ee od EAV-a, \u0161to ga \u010dini jo\u0161 boljim. Me\u0111utim, ovaj referentni test, naravno, ne pokriva sve aspekte (na primjer, entitete s vrlo velikim brojem svojstava, zna\u010dajnim pove\u0107anjem broja postojec\u0301ih svojstava,...), pa ako imate bilo kakvih prijedloga o tome kako ih pobolj\u0161ati, slobodno ostavite u komentarima!<br \/>\n<br \/>Izvor: <a content=\"nofollow\" rel=\"nofollow\" href=\"https:\/\/habr.com\/ru\/post\/475178\/\">habr.com<\/a><\/p>","protected":false,"gt_translate_keys":[{"key":"rendered","format":"html"}]},"excerpt":{"rendered":"<p>TL; DR: JSONB \u043c\u043e\u0436\u0435\u0442 \u0437\u043d\u0430\u0447\u0438\u0442\u0435\u043b\u044c\u043d\u043e \u0443\u043f\u0440\u043e\u0441\u0442\u0438\u0442\u044c \u0440\u0430\u0437\u0440\u0430\u0431\u043e\u0442\u043a\u0443 \u0441\u0445\u0435\u043c\u044b \u0411\u0414 \u0431\u0435\u0437 \u0443\u0449\u0435\u0440\u0431\u0430 \u043f\u0440\u043e\u0438\u0437\u0432\u043e\u0434\u0438\u0442\u0435\u043b\u044c\u043d\u043e\u0441\u0442\u0438 \u0432 \u0437\u0430\u043f\u0440\u043e\u0441\u0430\u0445. \u0412\u0432\u0435\u0434\u0435\u043d\u0438\u0435 \u041f\u0440\u0438\u0432\u0435\u0434\u0435\u043c \u043a\u043b\u0430\u0441\u0441\u0438\u0447\u0435\u0441\u043a\u0438\u0439 \u043f\u0440\u0438\u043c\u0435\u0440, \u043d\u0430\u0432\u0435\u0440\u043d\u043e\u0435, \u043e\u0434\u043d\u043e\u0433\u043e \u0438\u0437 \u0441\u0442\u0430\u0440\u0435\u0439\u0448\u0438\u0445 \u0432\u0430\u0440\u0438\u0430\u043d\u0442\u043e\u0432 \u0438\u0441\u043f\u043e\u043b\u044c\u0437\u043e\u0432\u0430\u043d\u0438\u044f \u0432 \u043c\u0438\u0440\u0435 \u0440\u0435\u043b\u044f\u0446\u0438\u043e\u043d\u043d\u044b\u0445 \u0411\u0414 (\u0431\u0430\u0437\u0430 \u0434\u0430\u043d\u043d\u044b\u0445): \u0443 \u043d\u0430\u0441 \u0435\u0441\u0442\u044c \u0441\u0443\u0449\u043d\u043e\u0441\u0442\u044c, \u0438 \u043d\u0435\u043e\u0431\u0445\u043e\u0434\u0438\u043c\u043e \u0441\u043e\u0445\u0440\u0430\u043d\u0438\u0442\u044c \u043e\u043f\u0440\u0435\u0434\u0435\u043b\u0435\u043d\u043d\u044b\u0435 \u0441\u0432\u043e\u0439\u0441\u0442\u0432\u0430 (\u0430\u0442\u0440\u0438\u0431\u0443\u0442\u044b) \u044d\u0442\u043e\u0439 \u0441\u0443\u0449\u043d\u043e\u0441\u0442\u0438. \u041d\u043e \u043d\u0435 \u0432\u0441\u0435 \u044d\u043a\u0437\u0435\u043c\u043f\u043b\u044f\u0440\u044b \u043c\u043e\u0433\u0443\u0442 \u0438\u043c\u0435\u044e\u0442 \u043e\u0434\u0438\u043d\u0430\u043a\u043e\u0432\u044b\u0439 \u043d\u0430\u0431\u043e\u0440 \u0441\u0432\u043e\u0439\u0441\u0442\u0432, \u043a \u0442\u043e\u043c\u0443 \u0436\u0435 \u0432 [&hellip;]<\/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-52584","post","type-post","status-publish","format-standard","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=\"TL; DR: JSONB \u043c\u043e\u0436\u0435\u0442 \u0437\u043d\u0430\u0447\u0438\u0442\u0435\u043b\u044c\u043d\u043e \u0443\u043f\u0440\u043e\u0441\u0442\u0438\u0442\u044c \u0440\u0430\u0437\u0440\u0430\u0431\u043e\u0442\u043a\u0443 \u0441\u0445\u0435\u043c\u044b \u0411\u0414 \u0431\u0435\u0437 \u0443\u0449\u0435\u0440\u0431\u0430 \u043f\u0440\u043e\u0438\u0437\u0432\u043e\u0434\u0438\u0442\u0435\u043b\u044c\u043d\u043e\u0441\u0442\u0438 \u0432 \u0437\u0430\u043f\u0440\u043e\u0441\u0430\u0445. \u0412\u0432\u0435\u0434\u0435\u043d\u0438\u0435 \u041f\u0440\u0438\u0432\u0435\u0434\u0435\u043c \u043a\u043b\u0430\u0441\u0441\u0438\u0447\u0435\u0441\u043a\u0438\u0439 \u043f\u0440\u0438\u043c\u0435\u0440, \u043d\u0430\u0432\u0435\u0440\u043d\u043e\u0435, \u043e\u0434\u043d\u043e\u0433\u043e \u0438\u0437 \u0441\u0442\u0430\u0440\u0435\u0439\u0448\u0438\u0445.\" \/>\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\/bs\/blog\/administrirovanie\/zamena-eav-na-jsonb-v-postgresql\" \/>\n\t\t<meta name=\"generator\" content=\"All in One SEO (AIOSEO) 5.0.5.1\" \/>\n\t\t<meta property=\"og:locale\" content=\"bs_BA\" \/>\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\u0430\u043c\u0435\u043d\u0430 EAV \u043d\u0430 JSONB \u0432 PostgreSQL | ProHoster\" \/>\n\t\t<meta property=\"og:description\" content=\"TL; DR: JSONB \u043c\u043e\u0436\u0435\u0442 \u0437\u043d\u0430\u0447\u0438\u0442\u0435\u043b\u044c\u043d\u043e \u0443\u043f\u0440\u043e\u0441\u0442\u0438\u0442\u044c \u0440\u0430\u0437\u0440\u0430\u0431\u043e\u0442\u043a\u0443 \u0441\u0445\u0435\u043c\u044b \u0411\u0414 \u0431\u0435\u0437 \u0443\u0449\u0435\u0440\u0431\u0430 \u043f\u0440\u043e\u0438\u0437\u0432\u043e\u0434\u0438\u0442\u0435\u043b\u044c\u043d\u043e\u0441\u0442\u0438 \u0432 \u0437\u0430\u043f\u0440\u043e\u0441\u0430\u0445. \u0412\u0432\u0435\u0434\u0435\u043d\u0438\u0435 \u041f\u0440\u0438\u0432\u0435\u0434\u0435\u043c \u043a\u043b\u0430\u0441\u0441\u0438\u0447\u0435\u0441\u043a\u0438\u0439 \u043f\u0440\u0438\u043c\u0435\u0440, \u043d\u0430\u0432\u0435\u0440\u043d\u043e\u0435, \u043e\u0434\u043d\u043e\u0433\u043e \u0438\u0437 \u0441\u0442\u0430\u0440\u0435\u0439\u0448\u0438\u0445.\" \/>\n\t\t<meta property=\"og:url\" content=\"https:\/\/prohoster.info\/bs\/blog\/administrirovanie\/zamena-eav-na-jsonb-v-postgresql\" \/>\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=\"2019-11-11T21:00:00+00:00\" \/>\n\t\t<meta property=\"article:modified_time\" content=\"2020-02-18T11:00:21+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\udd47Zamjena EAV-a s JSONB u PostgreSQL | ProHoster","description":"TL; DR: JSONB mo\u017ee zna\u010dajno pojednostaviti razvoj sheme baze podataka bez gubitka performansi u upitima. Uvod. Dajemo klasi\u010dan primer, verovatno jedan od najstarijih.","canonical_url":"https:\/\/prohoster.info\/bs\/blog\/administrirovanie\/zamena-eav-na-jsonb-v-postgresql","robots":"max-image-preview:large","keywords":"","webmasterTools":{"miscellaneous":""},"schema":null,"og:locale":"bs_BA","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\u0430\u043c\u0435\u043d\u0430 EAV \u043d\u0430 JSONB \u0432 PostgreSQL | ProHoster","og:description":"TL; DR: JSONB \u043c\u043e\u0436\u0435\u0442 \u0437\u043d\u0430\u0447\u0438\u0442\u0435\u043b\u044c\u043d\u043e \u0443\u043f\u0440\u043e\u0441\u0442\u0438\u0442\u044c \u0440\u0430\u0437\u0440\u0430\u0431\u043e\u0442\u043a\u0443 \u0441\u0445\u0435\u043c\u044b \u0411\u0414 \u0431\u0435\u0437 \u0443\u0449\u0435\u0440\u0431\u0430 \u043f\u0440\u043e\u0438\u0437\u0432\u043e\u0434\u0438\u0442\u0435\u043b\u044c\u043d\u043e\u0441\u0442\u0438 \u0432 \u0437\u0430\u043f\u0440\u043e\u0441\u0430\u0445. \u0412\u0432\u0435\u0434\u0435\u043d\u0438\u0435 \u041f\u0440\u0438\u0432\u0435\u0434\u0435\u043c \u043a\u043b\u0430\u0441\u0441\u0438\u0447\u0435\u0441\u043a\u0438\u0439 \u043f\u0440\u0438\u043c\u0435\u0440, \u043d\u0430\u0432\u0435\u0440\u043d\u043e\u0435, \u043e\u0434\u043d\u043e\u0433\u043e \u0438\u0437 \u0441\u0442\u0430\u0440\u0435\u0439\u0448\u0438\u0445.","og:url":"https:\/\/prohoster.info\/bs\/blog\/administrirovanie\/zamena-eav-na-jsonb-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-11-11T21:00:00+00:00","article:modified_time":"2020-02-18T11:00:21+00:00","article:publisher":"https:\/\/www.facebook.com\/prohoster","article:author":"https:\/\/www.facebook.com\/prohoster"},"aioseo_meta_data":{"post_id":"52584","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-24 04:07:19","breadcrumb_settings":null,"limit_modified_date":false,"reviewed_by":null,"ai":null,"created":"2021-02-28 20:40:27","updated":"2026-01-24 04:07:19","focus_keyword":null,"additional_keywords":null,"truseo_locale":null},"gt_translate_keys":[{"key":"link","format":"url"}],"_links":{"self":[{"href":"https:\/\/prohoster.info\/bs\/wp-json\/wp\/v2\/posts\/52584","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/prohoster.info\/bs\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/prohoster.info\/bs\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/prohoster.info\/bs\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/prohoster.info\/bs\/wp-json\/wp\/v2\/comments?post=52584"}],"version-history":[{"count":0,"href":"https:\/\/prohoster.info\/bs\/wp-json\/wp\/v2\/posts\/52584\/revisions"}],"wp:attachment":[{"href":"https:\/\/prohoster.info\/bs\/wp-json\/wp\/v2\/media?parent=52584"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/prohoster.info\/bs\/wp-json\/wp\/v2\/categories?post=52584"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/prohoster.info\/bs\/wp-json\/wp\/v2\/tags?post=52584"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}