{"id":79039,"date":"2020-04-23T19:43:26","date_gmt":"2020-04-23T17:43:26","guid":{"rendered":"https:\/\/prohoster.info\/blog\/administrirovanie\/ekonomim-kopeechku-na-bolshih-obemah-v-postgresql"},"modified":"2020-04-23T19:43:26","modified_gmt":"2020-04-23T17:43:26","slug":"ekonomim-kopeechku-na-bolshih-obemah-v-postgresql","status":"publish","type":"post","link":"https:\/\/prohoster.info\/bs\/blog\/administrirovanie\/ekonomim-kopeechku-na-bolshih-obemah-v-postgresql","title":{"rendered":"\u0160tedimo novac na velikim koli\u010dinama u PostgreSQL-u","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"<p>Nastavljaju\u0107i temu snimanja velikih tokova podataka, pokrenutu <noindex><a rel=\"nofollow\" href=\"https:\/\/habr.com\/ru\/post\/497008\/\">prethodnim \u010dlankom o particionisanju<\/a><\/noindex>, u ovom \u0107emo razmotriti na\u010dine na koje se mo\u017ee <b>smanjiti \u201efizi\u010dka\u201c veli\u010dina pohranjenog<\/b> u PostgreSQL-u, i njihov uticaj na performanse servera.<\/p>\n<p>Govori\u0107emo o <b>TOAST pode\u0161avanjima i poravnanju podataka<\/b>. \u201eU proseku\u201c, ove metode \u0107e omogu\u0107iti u\u0161tedu ne previ\u0161e resursa, ali \u2014 ukupno bez modifikacije koda aplikacije.<\/p>\n<p><img decoding=\"async\" alt=\"\u0160tedimo novac na velikim koli\u010dinama u PostgreSQL-u\" src=\"\/wp-content\/uploads\/2020\/04\/4d43b9b43edb10c4c8f13159c7dd1eac.jpg\" style=\"display:block;margin: 0 auto;\" \/><br \/>\nMe\u0111utim, na\u0161e iskustvo se pokazalo veoma produktivnim u tom pogledu, jer su skladi\u0161ta skoro svakog monitoringa po svojoj prirodi <b>ve\u0107inom append-only<\/b> naro\u010dito u pogledu zapisivanih podataka. I ako vas zanima kako se mo\u017ee nau\u010diti baza da pi\u0161e na disk umesto <b>200MB\/s<\/b> dvostruko manje \u2014 molim vas, nastavite sa \u010ditanjem.<br \/>\n<noindex><a rel=\"nofollow\" name=\"habracut\"><\/a><\/noindex><\/p>\n<h2>Mali trikovi velikih podataka<\/h2>\n<p>\nNa profilu rada <noindex><a rel=\"nofollow\" href=\"https:\/\/habr.com\/ru\/post\/487380\/\">na\u0161eg servisa<\/a><\/noindex>, redovno dobijamo iz logova <b>tekstualne pakete<\/b>.<\/p>\n<p>A po\u0161to <noindex><a rel=\"nofollow\" href=\"https:\/\/sbis.ru\/all_services\">kompleks SBIS<\/a><\/noindex>, \u010dije baze podataka pratimo, predstavlja vi\u0161ekomponentni proizvod sa slo\u017eenim strukturama podataka, tako i upiti <b>za postizanje maksimalne performanse<\/b> se pokazali kao <noindex><a rel=\"nofollow\" href=\"https:\/\/habr.com\/ru\/post\/486072\/\">\u201emnogotominci\u201c sa slo\u017eenom algoritamskom logikom<\/a><\/noindex>. Tako da i obim svakog pojedina\u010dnog upita ili rezultantnog plana izvr\u0161enja u logu koji dobijamo ispostavlja se da je \u201eu proseku\u201c prili\u010dno veliki.<\/p>\n<p>Hajde da pogledamo strukturu jedne od tabela u koju unosimo \u201esirove\u201c podatke \u2014 to jest direktno originalni tekst iz zapisnika:<\/p>\n<pre><code class=\"sql\">CREATE TABLE rawdata_orig(\n  pack -- PK\n    uuid NOT NULL\n, recno -- PK\n    smallint NOT NULL\n, dt -- klju\u010d sekcije\n    date\n, data -- najva\u017enija stvar\n    text\n, PRIMARY KEY(pack, recno)\n);<\/code><\/pre>\n<p>\nTipi\u010dna takva tabelica (ve\u0107 particionisana, naravno, zato je ovo \u2014 \u0161ablon sekcije), gde je najva\u017enije \u2014 tekst. Ponekad prili\u010dno obiman.<\/p>\n<p>Setimo se da \u201efizi\u010dka\u201c veli\u010dina jednog zapisa u PG ne mo\u017ee zauzimati vi\u0161e od jedne stranice podataka, ali \u201elogi\u010dka\u201c veli\u010dina \u2014 to je sasvim druga stvar. Da bi se u funkciji zadr\u017ealo obimno vrednost (varchar\/text\/bytea) koristi se <noindex><a rel=\"nofollow\" href=\"https:\/\/postgrespro.ru\/docs\/postgresql\/12\/storage-toast\">TOAST tehnologija<\/a><\/noindex>:<\/p>\n<blockquote><p>PostgreSQL koristi fiksnu veli\u010dinu stranice (obi\u010dno 8 KB) i ne dopu\u0161ta da tuplje zauzimaju vi\u0161e stranica. Zbog toga nije mogu\u0107e direktno skladi\u0161titi vrlo velike vrijednosti polja. Da bi se prevazi\u0161la ova ograni\u010denja, velike vrijednosti polja se kompresuju i\\\/ili razbijaju na nekoliko fizi\u010dkih redova. Ovo se de\u0161ava neprimjetno za korisnika i na ve\u0107i dio koda servera uti\u010de neznatno. Ova metoda je poznata kao TOAST ...<\/p><\/blockquote>\n<p>\nU stvari, za svaku tabelu sa \u201epotencijalno velikim\u201c poljima automatski <noindex><a rel=\"nofollow\" href=\"https:\/\/postgrespro.ru\/docs\/postgresql\/12\/storage-toast#STORAGE-TOAST-ONDISK\">se kreira povezana tabela sa \u201edeljenjem\u201c<\/a><\/noindex> svake \u201evelike\u201c stavke u segmente od 2KB:<\/p>\n<pre><code class=\"sql\">TOAST(\n  chunk_id\n    integer\n, chunk_seq\n    integer\n, chunk_data\n    bytea\n, PRIMARY KEY(chunk_id, chunk_seq)\n);<\/code><\/pre>\n<p>\nTo jest, ukoliko moramo da zape\u010datimo red sa \u201evelikom\u201c vredno\u0161\u0107u <code>data<\/code>, stvarna zapisivanje \u0107e se dogoditi <b>ne samo u glavnoj tabeli i njenom PK, ve\u0107 i u TOAST-u i njegovom PK<\/b>.<\/p>\n<h4>Smanjivanje TOAST-uticaja<\/h4>\n<p>\nAli ve\u0107ina zapisa kod nas ipak nije toliko velika, <b>u 8KB bi se trebali uklapati<\/b> \u2014 kako u\u0161tedeti na tome?..<\/p>\n<p>Tada nam poma\u017ee atribut <noindex><a rel=\"nofollow\" href=\"https:\/\/postgrespro.ru\/docs\/postgresql\/12\/storage-toast#STORAGE-TOAST-ONDISK\"><code>STORAGE<\/code><\/a><\/noindex> u koloni tabele:<\/p>\n<blockquote>\n<ul>\n<li><b>EXTENDED<\/b> omogu\u0107ava kako kompresiju, tako i odvojeno skladi\u0161tenje. Ovo <b>je standardna opcija<\/b> za ve\u0107inu tipova podataka kompatibilnih sa TOAST-om. Prvo se poku\u0161ava izvr\u0161iti kompresija, zatim \u2014 \u010duvanje van tabele, ukoliko red jo\u0161 uvek bude prevelik.<\/li>\n<li><b>MAIN<\/b> omogu\u0107ava kompresiju, ali ne i odvojeno skladi\u0161tenje. (U stvari, odvojeno skladi\u0161tenje \u0107e se me\u0111utim izvr\u0161iti za takve kolone, ali samo <b>kao krajnje sredstvo<\/b>, kada nema drugog na\u010dina da se smanji red tako da stane na stranicu.)<\/li>\n<\/ul>\n<\/blockquote>\n<p>U stvari, to je upravo ono \u0161to nam treba za tekst \u2014 <b>maksimalno kompresovati, a ako ba\u0161 ne mo\u017ee da stane \u2014 izneti u TOAST<\/b>. Ovo se mo\u017ee uraditi direktno \u201eu hodu\u201c, jednom komandom:<\/p>\n<pre><code class=\"sql\">ALTER TABLE rawdata_orig ALTER COLUMN data SET STORAGE MAIN;<\/code><\/pre>\n<p><\/p>\n<h4>Kako proceniti efekat<\/h4>\n<p>\nPo\u0161to se svaki dan tok podataka menja, ne mo\u017eemo upore\u0111ivati apsolutne cifre, ali u relativnim uslovima \u0161to <b>manji deo<\/b> smo zabele\u017eili u TOAST-u \u2014 to bolje. Ali ovde postoji opasnost \u2014 \u0161to je ve\u0107i \u201efizi\u010dki\u201c obim svake pojedina\u010dne stavke, to se indeks \u201e\u0161iri\u201c, jer je potrebno pokriti ve\u0107i broj stranica podataka.<\/p>\n<p>Sekcija <b>pre promena<\/b>:<\/p>\n<pre><code class=\"plaintext\">heap  = 37GB (39%)\nTOAST = 54GB (57%)\nPK    =  4GB ( 4%)\n<\/code><\/pre>\n<p>\nSekcija <b>posle promena<\/b>:<\/p>\n<pre><code class=\"plaintext\">heap  = 37GB (67%)\nTOAST = 16GB (29%)\nPK    =  2GB ( 4%)<\/code><\/pre>\n<p>\nU stvari, mi <b>po\u010deli smo pisati u TOAST dvostruko re\u0111e<\/b>, \u0161to je rasteretilo ne samo disk, ve\u0107 i CPU:<\/p>\n<p><img decoding=\"async\" alt=\"\u0160tedimo novac na velikim koli\u010dinama u PostgreSQL-u\" src=\"\/wp-content\/uploads\/2020\/04\/547485eff9c6491ffe4d59e5c81f656d.jpg\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<img decoding=\"async\" alt=\"\u0160tedimo novac na velikim koli\u010dinama u PostgreSQL-u\" src=\"\/wp-content\/uploads\/2020\/04\/6bd3b18146c20959693f961e41fff447.jpg\" style=\"display:block;margin: 0 auto;\" \/><br \/>\nNapominjem da smo sada manje \"\u010ditaju\u0107i\" disk, ne samo \"pi\u0161u\u0107i\" - jer prilikom umetanja zapisa u neku tabelu moramo \"pro\u010ditati\" i deo stabla svakog od indeksa kako bismo odredili njenu budu\u0107u poziciju u njima.<\/p>\n<h2>Kome je dobro \u017eiveti na PostgreSQL 11<\/h2>\n<p>\nNakon a\u017euriranja na PG11, odlu\u010dili smo da nastavimo s \"tuningom\" TOAST-a i obratili smo pa\u017enju da je od ove verzije postao dostupan za pode\u0161avanje parametar <noindex><a rel=\"nofollow\" href=\"https:\/\/postgrespro.ru\/docs\/postgresql\/11\/storage-toast#STORAGE-TOAST-ONDISK\"><code>toast_tuple_target<\/code><\/a><\/noindex>:<\/p>\n<blockquote><p>Kod obrade TOAST-a se aktivira samo kada je veli\u010dina niza koji treba sa\u010duvati u tabeli ve\u0107a od TOAST_TUPLE_THRESHOLD bajta (obi\u010dno to iznosi 2 KB). TOAST kod \u0107e kompresovati i\/ili izneti vrednosti polja izvan tabele sve dok vrednost niza ne postane manja od TOAST_TUPLE_TARGET bajta (varijabilna veli\u010dina, tako\u0111e obi\u010dno 2 KB) ili ne\u0107e biti mogu\u0107e smanjiti obim.<\/p><\/blockquote>\n<p>Odlu\u010dili smo da su na\u0161i podaci obi\u010dno ili \"veoma kratki\" ili odmah \"veoma dugi\", pa smo se odlu\u010dili ograni\u010diti na minimalno mogu\u0107u vrednost:<\/p>\n<pre><code class=\"sql\">ALTER TABLE rawplan_orig SET (toast_tuple_target = 128);<\/code><\/pre>\n<p>\nHajde da vidimo kako su nove postavke uticale na optere\u0107enje diska nakon ponovne konfiguracije:<\/p>\n<p><img decoding=\"async\" alt=\"\u0160tedimo novac na velikim koli\u010dinama u PostgreSQL-u\" src=\"\/wp-content\/uploads\/2020\/04\/ccaa4879e413a566b362d01582eb8c19.jpg\" style=\"display:block;margin: 0 auto;\" \/><br \/>\nNije lo\u0161e! Prose\u010dna <b>\u010dekanje na disk se smanjilo<\/b> otprilike 1.5 puta, a \"zauzetost\" diska - za 20%! Ali mo\u017eda je to nekako uticalo na CPU?<\/p>\n<p><img decoding=\"async\" alt=\"\u0160tedimo novac na velikim koli\u010dinama u PostgreSQL-u\" src=\"\/wp-content\/uploads\/2020\/04\/f7026e5809853d35c6fb7a8376b9f369.jpg\" style=\"display:block;margin: 0 auto;\" \/><br \/>\nBar, sigurno nije postalo gore. Iako, te\u0161ko je suditi ako ni ovoliki obim ne mo\u017ee podi\u0107i prose\u010dno optere\u0107enje CPU-a iznad <b>5%<\/b>.<\/p>\n<h2>Promenom mesta zagrada suma... menja se!<\/h2>\n<p>\nKao \u0161to je poznato, dinar \u010duva rubalja, i pri na\u0161im obimima skladi\u0161tenja od <b>10TB\/mese\u010dno<\/b> \u010dak i mala optimizacija mo\u017ee doneti dobar profit. Zato smo obratili pa\u017enju na fizi\u010dku strukturu svojih podataka - kako su konkretno <b>\"slo\u017eena\" polja unutar zapisa<\/b> svake od tabela.<\/p>\n<p>Zato \u0161to zbog <noindex><a rel=\"nofollow\" href=\"https:\/\/habr.com\/ru\/company\/postgrespro\/blog\/444536\/\">poravnavanja podataka<\/a><\/noindex> to direktno <noindex><a rel=\"nofollow\" href=\"https:\/\/docs.gitlab.com\/ee\/development\/ordering_table_columns.html\">utje\u010de na rezultantni volumen<\/a><\/noindex>:<\/p>\n<blockquote><p>Mnoge arhitekture predvi\u0111aju poravnavanje podataka prema granicama ma\u0161inskih re\u010di. Na primer, na 32-bitnom sistemu x86, celobrojne vrednosti (tip integer, zauzima 4 bajta) bi\u0107e poravnate prema granici 4-bajtnih re\u010di, kao i brojevi sa pomi\u010dnom ta\u010dkom dvostruke preciznosti (tip double precision, 8 bajtova). A na 64-bitnom sistemu vrednosti double \u0107e biti poravnate prema granici 8-bajtnih re\u010di. Ovo je jo\u0161 jedan razlog nespojivosti.<\/p>\n<p>Zbog poravnanja, veli\u010dina redova u tabeli zavisi od redosleda polja. Obi\u010dno ovaj efekat nije previ\u0161e vidljiv, ali u nekim slu\u010dajevima mo\u017ee dovesti do zna\u010dajnog pove\u0107anja veli\u010dine. Na primer, ako su polja tipova char(1) i integer pome\u0161ana, izme\u0111u njih \u0107e se obi\u010dno izgubiti 3 bajta.<\/p><\/blockquote>\n<p>\nHajde da po\u010dnemo sa sinteti\u010dkim modelima:<\/p>\n<pre><code class=\"sql\">SELECT pg_column_size(ROW(\n  '0000-0000-0000-0000-0000-0000-0000-0000'::uuid\n, 0::smallint\n, '2019-01-01'::date\n));\n-- 48 bajtova\n\nSELECT pg_column_size(ROW(\n  '2019-01-01'::date\n, '0000-0000-0000-0000-0000-0000-0000-0000'::uuid\n, 0::smallint\n));\n-- 46 bajtova<\/code><\/pre>\n<p>\nOdakle dolaze ta dva vi\u0161ka bajta u prvom slu\u010daju? Sve je prosto \u2014 <b>2-bajtni smallint se poravnava na 4-bajtnoj granici<\/b> pre slede\u0107eg polja, a kada je poslednji \u2014 nema gde da se poravna i nema potrebe.<\/p>\n<p>U teoriji \u2014 sve je u redu i mo\u017eemo da pomeramo polja kako god \u017eelimo. Hajde da proverimo na realnim podacima na primeru jedne od tabela, \u010dija dnevna sekcija zauzima po 10-15GB.<\/p>\n<p>Po\u010detna struktura:<\/p>\n<pre><code class=\"sql\">CREATE TABLE public.plan_20190220\n(\n-- Nasle\u0111eno iz tabele plan:  pack uuid NOT NULL,\n-- Nasle\u0111eno iz tabele plan:  recno smallint NOT NULL,\n-- Nasle\u0111eno iz tabele plan:  host uuid,\n-- Nasle\u0111eno iz tabele plan:  ts timestamp with time zone,\n-- Nasle\u0111eno iz tabele plan:  exectime numeric(32,3),\n-- Nasle\u0111eno iz tabele plan:  duration numeric(32,3),\n-- Nasle\u0111eno iz tabele plan:  bufint bigint,\n-- Nasle\u0111eno iz tabele plan:  bufmem bigint,\n-- Nasle\u0111eno iz tabele plan:  bufdsk bigint,\n-- Nasle\u0111eno iz tabele plan:  apn uuid,\n-- Nasle\u0111eno iz tabele plan:  ptr uuid,\n-- Nasle\u0111eno iz tabele plan:  dt date,\n  CONSTRAINT plan_20190220_pkey PRIMARY KEY (pack, recno),\n  CONSTRAINT chck_ptr CHECK (ptr IS NOT NULL),\n  CONSTRAINT plan_20190220_dt_check CHECK (dt = '2019-02-20'::date)\n)\nINHERITS (public.plan)<\/code><\/pre>\n<p>\nSekcija nakon promene reda kolona \u2014 to\u010dno <b>isti polja, samo je redosled druga\u010diji<\/b>:<\/p>\n<pre><code class=\"sql\">CREATE TABLE public.plan_20190221\n(\n-- Nasle\u0111eno iz tabele plan:  dt date NOT NULL,\n-- Nasle\u0111eno iz tabele plan:  ts timestamp with time zone,\n-- Nasle\u0111eno iz tabele plan:  pack uuid NOT NULL,\n-- Nasle\u0111eno iz tabele plan:  recno smallint NOT NULL,\n-- Nasle\u0111eno iz tabele plan:  host uuid,\n-- Nasle\u0111eno iz tabele plan:  apn uuid,\n-- Nasle\u0111eno iz tabele plan:  ptr uuid,\n-- Nasle\u0111eno iz tabele plan:  bufint bigint,\n-- Nasle\u0111eno iz tabele plan:  bufmem bigint,\n-- Nasle\u0111eno iz tabele plan:  bufdsk bigint,\n-- Nasle\u0111eno iz tabele plan:  exectime numeric(32,3),\n-- Nasle\u0111eno iz tabele plan:  duration numeric(32,3),\n  CONSTRAINT plan_20190221_pkey PRIMARY KEY (pack, recno),\n  CONSTRAINT chck_ptr CHECK (ptr IS NOT NULL),\n  CONSTRAINT plan_20190221_dt_check CHECK (dt = '2019-02-21'::date)\n)\nINHERITS (public.plan)<\/code><\/pre>\n<p>\nUkupna veli\u010dina sekcije odre\u0111ena je koli\u010dinom \u201e\u010dinjenica\u201c i zavisi samo od spoljnih procesa, tako da \u0107emo podeliti veli\u010dinu heap (<code>pg_relation_size<\/code>) o broju zapisa u njemu \u2014 dakle, dobijamo <b>prose\u010dnu veli\u010dinu stvarnog sa\u010duvanog zapisa<\/b>:<\/p>\n<p><img decoding=\"async\" alt=\"\u0160tedimo novac na velikim koli\u010dinama u PostgreSQL-u\" src=\"\/wp-content\/uploads\/2020\/04\/06be2d7d70d223e7678f9a478e4c293f.jpg\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<b>Minus 6% volumena<\/b>, odli\u010dno!<\/p>\n<p>Ali, naravno, nije sve tako ru\u017ei\u010dasto \u2014 jer <b>ne mo\u017eemo promeniti redosled polja u indeksima<\/b>, pa stoga \u201eu celini\u201c (<code>pg_total_relation_size<\/code>)\u2026<\/p>\n<p><img decoding=\"async\" alt=\"\u0160tedimo novac na velikim koli\u010dinama u PostgreSQL-u\" src=\"\/wp-content\/uploads\/2020\/04\/8beff38e5034fc0d40665b75cb3b3625.jpg\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n\u2026 ipak i tu <b>u\u0161te\u0111ena su 1.5%<\/b>, ne menjaju\u0107i ni jedan red koda. Tako je!<\/p>\n<p><img decoding=\"async\" alt=\"\u0160tedimo novac na velikim koli\u010dinama u PostgreSQL-u\" src=\"\/wp-content\/uploads\/2020\/04\/10f4a2151465a38bf45823a5d360302b.jpg\" style=\"display:block;margin: 0 auto;\" \/><\/p>\n<p>Napominjem da navedena raspodela polja nije sigurno najsavr\u0161enija. Jer neka polja ne \u017eelimo da \u201erazdvajamo\u201c iz estetskih razloga \u2014 na primer, par <code>(pack, recno)<\/code>, koji predstavlja PK za ovu tabelu.<\/p>\n<p>U principu, definicija \u201eminimalnog\u201c rasporeda polja je prili\u010dno jednostavna \u201eizborna\u201c zada\u0107a. Stoga mo\u017eete na svojim podacima dobiti rezultate \u010dak bolje nego mi \u2014 poku\u0161ajte!<br \/>\n<br \/>Izvor: <a content=\"nofollow\" rel=\"nofollow\" href=\"https:\/\/habr.com\/ru\/company\/tensor\/blog\/498292\/\">habr.com<\/a> <\/p>","protected":false,"gt_translate_keys":[{"key":"rendered","format":"html"}]},"excerpt":{"rendered":"<p>\u041f\u0440\u043e\u0434\u043e\u043b\u0436\u0430\u044f \u0442\u0435\u043c\u0443 \u0437\u0430\u043f\u0438\u0441\u0438 \u0431\u043e\u043b\u044c\u0448\u0438\u0445 \u043f\u043e\u0442\u043e\u043a\u043e\u0432 \u0434\u0430\u043d\u043d\u044b\u0445, \u043f\u043e\u0434\u043d\u044f\u0442\u0443\u044e \u043f\u0440\u0435\u0434\u044b\u0434\u0443\u0449\u0435\u0439 \u0441\u0442\u0430\u0442\u044c\u0435\u0439 \u043f\u0440\u043e \u0441\u0435\u043a\u0446\u0438\u043e\u043d\u0438\u0440\u043e\u0432\u0430\u043d\u0438\u0435, \u0432 \u044d\u0442\u043e\u0439 \u0440\u0430\u0441\u0441\u043c\u043e\u0442\u0440\u0438\u043c \u0441\u043f\u043e\u0441\u043e\u0431\u044b, \u043a\u043e\u0442\u043e\u0440\u044b\u043c\u0438 \u043c\u043e\u0436\u043d\u043e \u0443\u043c\u0435\u043d\u044c\u0448\u0438\u0442\u044c \u00ab\u0444\u0438\u0437\u0438\u0447\u0435\u0441\u043a\u0438\u0439\u00bb \u0440\u0430\u0437\u043c\u0435\u0440 \u0445\u0440\u0430\u043d\u0438\u043c\u043e\u0433\u043e \u0432 PostgreSQL, \u0438 \u0438\u0445 \u0432\u043b\u0438\u044f\u043d\u0438\u0435 \u043d\u0430 \u043f\u0440\u043e\u0438\u0437\u0432\u043e\u0434\u0438\u0442\u0435\u043b\u044c\u043d\u043e\u0441\u0442\u044c \u0441\u0435\u0440\u0432\u0435\u0440\u0430. \u0420\u0435\u0447\u044c \u043f\u043e\u0439\u0434\u0435\u0442 \u043f\u0440\u043e \u043d\u0430\u0441\u0442\u0440\u043e\u0439\u043a\u0438 TOAST \u0438 \u0432\u044b\u0440\u0430\u0432\u043d\u0438\u0432\u0430\u043d\u0438\u0435 \u0434\u0430\u043d\u043d\u044b\u0445. \u00ab\u0412 \u0441\u0440\u0435\u0434\u043d\u0435\u043c\u00bb \u044d\u0442\u0438 \u0441\u043f\u043e\u0441\u043e\u0431\u044b \u043f\u043e\u0437\u0432\u043e\u043b\u044f\u0442 \u0441\u044d\u043a\u043e\u043d\u043e\u043c\u0438\u0442\u044c \u043d\u0435 \u0441\u043b\u0438\u0448\u043a\u043e\u043c \u043c\u043d\u043e\u0433\u043e \u0440\u0435\u0441\u0443\u0440\u0441\u043e\u0432, \u0437\u0430\u0442\u043e \u2014 \u0432\u043e\u043e\u0431\u0449\u0435 \u0431\u0435\u0437 \u043c\u043e\u0434\u0438\u0444\u0438\u043a\u0430\u0446\u0438\u0438 \u043a\u043e\u0434\u0430 \u043f\u0440\u0438\u043b\u043e\u0436\u0435\u043d\u0438\u044f. \u041e\u0434\u043d\u0430\u043a\u043e, [&hellip;]<\/p>\n","protected":false,"gt_translate_keys":[{"key":"rendered","format":"html"}]},"author":1,"featured_media":79040,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[688],"tags":[],"class_list":["post-79039","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\u043e\u0434\u043e\u043b\u0436\u0430\u044f \u0442\u0435\u043c\u0443 \u0437\u0430\u043f\u0438\u0441\u0438 \u0431\u043e\u043b\u044c\u0448\u0438\u0445 \u043f\u043e\u0442\u043e\u043a\u043e\u0432 \u0434\u0430\u043d\u043d\u044b\u0445, \u043f\u043e\u0434\u043d\u044f\u0442\u0443\u044e \u043f\u0440\u0435\u0434\u044b\u0434\u0443\u0449\u0435\u0439 \u0441\u0442\u0430\u0442\u044c\u0435\u0439 \u043f\u0440\u043e \u0441\u0435\u043a\u0446\u0438\u043e\u043d\u0438\u0440\u043e\u0432\u0430\u043d\u0438\u0435, \u0432 \u044d\u0442\u043e\u0439 \u0440\u0430\u0441\u0441\u043c\u043e\u0442\u0440\u0438\u043c \u0441\u043f\u043e\u0441\u043e\u0431\u044b, \u043a\u043e\u0442\u043e\u0440\u044b\u043c\u0438 \u043c\u043e\u0436\u043d\u043e.\" \/>\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\/ekonomim-kopeechku-na-bolshih-obemah-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\u042d\u043a\u043e\u043d\u043e\u043c\u0438\u043c \u043a\u043e\u043f\u0435\u0435\u0447\u043a\u0443 \u043d\u0430 \u0431\u043e\u043b\u044c\u0448\u0438\u0445 \u043e\u0431\u044a\u0435\u043c\u0430\u0445 \u0432 PostgreSQL | ProHoster\" \/>\n\t\t<meta property=\"og:description\" content=\"\u041f\u0440\u043e\u0434\u043e\u043b\u0436\u0430\u044f \u0442\u0435\u043c\u0443 \u0437\u0430\u043f\u0438\u0441\u0438 \u0431\u043e\u043b\u044c\u0448\u0438\u0445 \u043f\u043e\u0442\u043e\u043a\u043e\u0432 \u0434\u0430\u043d\u043d\u044b\u0445, \u043f\u043e\u0434\u043d\u044f\u0442\u0443\u044e \u043f\u0440\u0435\u0434\u044b\u0434\u0443\u0449\u0435\u0439 \u0441\u0442\u0430\u0442\u044c\u0435\u0439 \u043f\u0440\u043e \u0441\u0435\u043a\u0446\u0438\u043e\u043d\u0438\u0440\u043e\u0432\u0430\u043d\u0438\u0435, \u0432 \u044d\u0442\u043e\u0439 \u0440\u0430\u0441\u0441\u043c\u043e\u0442\u0440\u0438\u043c \u0441\u043f\u043e\u0441\u043e\u0431\u044b, \u043a\u043e\u0442\u043e\u0440\u044b\u043c\u0438 \u043c\u043e\u0436\u043d\u043e.\" \/>\n\t\t<meta property=\"og:url\" content=\"https:\/\/prohoster.info\/bs\/blog\/administrirovanie\/ekonomim-kopeechku-na-bolshih-obemah-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=\"2020-04-23T17:43:26+00:00\" \/>\n\t\t<meta property=\"article:modified_time\" content=\"2020-04-23T17:43:26+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\udd47\u0160tedimo nov\u010di\u0107 na velikim volumenima u PostgreSQL | ProHoster","description":"Nastavljaju\u0107i temu snimanja velikih tokova podataka, pokrenutu prethodnim \u010dlankom o particionisanju, razmotri\u0107emo na\u010dine na koje to mo\u017eemo.","canonical_url":"https:\/\/prohoster.info\/bs\/blog\/administrirovanie\/ekonomim-kopeechku-na-bolshih-obemah-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\u042d\u043a\u043e\u043d\u043e\u043c\u0438\u043c \u043a\u043e\u043f\u0435\u0435\u0447\u043a\u0443 \u043d\u0430 \u0431\u043e\u043b\u044c\u0448\u0438\u0445 \u043e\u0431\u044a\u0435\u043c\u0430\u0445 \u0432 PostgreSQL | ProHoster","og:description":"\u041f\u0440\u043e\u0434\u043e\u043b\u0436\u0430\u044f \u0442\u0435\u043c\u0443 \u0437\u0430\u043f\u0438\u0441\u0438 \u0431\u043e\u043b\u044c\u0448\u0438\u0445 \u043f\u043e\u0442\u043e\u043a\u043e\u0432 \u0434\u0430\u043d\u043d\u044b\u0445, \u043f\u043e\u0434\u043d\u044f\u0442\u0443\u044e \u043f\u0440\u0435\u0434\u044b\u0434\u0443\u0449\u0435\u0439 \u0441\u0442\u0430\u0442\u044c\u0435\u0439 \u043f\u0440\u043e \u0441\u0435\u043a\u0446\u0438\u043e\u043d\u0438\u0440\u043e\u0432\u0430\u043d\u0438\u0435, \u0432 \u044d\u0442\u043e\u0439 \u0440\u0430\u0441\u0441\u043c\u043e\u0442\u0440\u0438\u043c \u0441\u043f\u043e\u0441\u043e\u0431\u044b, \u043a\u043e\u0442\u043e\u0440\u044b\u043c\u0438 \u043c\u043e\u0436\u043d\u043e.","og:url":"https:\/\/prohoster.info\/bs\/blog\/administrirovanie\/ekonomim-kopeechku-na-bolshih-obemah-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":"2020-04-23T17:43:26+00:00","article:modified_time":"2020-04-23T17:43:26+00:00","article:publisher":"https:\/\/www.facebook.com\/prohoster","article:author":"https:\/\/www.facebook.com\/prohoster"},"aioseo_meta_data":{"post_id":"79039","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 16:46:33","updated":"2022-09-28 06:02:32","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\/79039","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=79039"}],"version-history":[{"count":0,"href":"https:\/\/prohoster.info\/bs\/wp-json\/wp\/v2\/posts\/79039\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/prohoster.info\/bs\/wp-json\/wp\/v2\/media\/79040"}],"wp:attachment":[{"href":"https:\/\/prohoster.info\/bs\/wp-json\/wp\/v2\/media?parent=79039"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/prohoster.info\/bs\/wp-json\/wp\/v2\/categories?post=79039"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/prohoster.info\/bs\/wp-json\/wp\/v2\/tags?post=79039"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}