{"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\/sl\/blog\/administrirovanie\/ekonomim-kopeechku-na-bolshih-obemah-v-postgresql","title":{"rendered":"\u0160tedimo malo novca na velikim koli\u010dinama u PostgreSQL-u","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"<p>Nadaljujemo temo zapisovanja velikih podatkovnih tokov, ki smo jo za\u010deli <noindex><a rel=\"nofollow\" href=\"https:\/\/habr.com\/ru\/post\/497008\/\">v prej\u0161njem \u010dlanku o sekcioniranju<\/a><\/noindex>, v tem pa bomo obravnavali na\u010dine, kako lahko <b>zmanj\u0161amo \u201efizi\u010dno\u201c velikost shranjenih<\/b> v PostgreSQL in njihov vpliv na zmogljivost stre\u017enika.<\/p>\n<p>Govora bo o <b>nastavitvah TOAST in poravnavanju podatkov<\/b>. \u201eV povpre\u010dju\u201c ti na\u010dini ne bodo prihranili preve\u010d virov, vendar - povsem brez modifikacije kode aplikacije.<\/p>\n<p><img decoding=\"async\" alt=\"\u0160tedimo malo novca na velikim koli\u010dinama u PostgreSQL-u\" src=\"\/wp-content\/uploads\/2020\/04\/4d43b9b43edb10c4c8f13159c7dd1eac.jpg\" style=\"display:block;margin: 0 auto;\" \/><br \/>\nNa\u0161e izku\u0161nje pa so se izkazale za zelo produktivne na tem podro\u010dju, saj je shranjevanje skoraj vseh monitoriranj po svoji naravi <b>ve\u010dinoma append-only<\/b> glede na zapisane podatke. In \u010de vas zanima, kako lahko nau\u010dite bazo pisati na disk namesto <b>200MB\/s<\/b> dvakrat manj - prosim, preberite naprej.<br \/>\n<noindex><a rel=\"nofollow\" name=\"habracut\"><\/a><\/noindex><\/p>\n<h2>Majhne skrivnosti velikih podatkov<\/h2>\n<p>\nGlede na profil dela <noindex><a rel=\"nofollow\" href=\"https:\/\/habr.com\/ru\/post\/487380\/\">na\u0161e storitve<\/a><\/noindex>, redno prejemamo iz registrov <b>besedilne pakete<\/b>.<\/p>\n<p>Ker <noindex><a rel=\"nofollow\" href=\"https:\/\/sbis.ru\/all_services\">kompleks SBIS<\/a><\/noindex>, katere podatkovne baze monitoriramo, je ve\u010dkomponentni produkt s kompleksnimi podatkovnimi strukturami, so tudi poizvedbe <b>za dosego maksimalne zmogljivosti<\/b> zelo <noindex><a rel=\"nofollow\" href=\"https:\/\/habr.com\/ru\/post\/486072\/\">\u201eve\u010dzvezdni\u0161ki\u201c s kompleksno algoritmi\u010dno logiko<\/a><\/noindex>. Tako da je obseg vsake posamezne poizvedbe ali rezultatnega na\u010drta izvedbe v logu, ki ga prejmemo, v povpre\u010dju kar velik.<\/p>\n<p>Poglejmo strukturo ene od tabel, v katero zapisujemo \u201esurove\u201c podatke - torej izvirno besedilo iz registra:<\/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 -- najpomembnej\u0161e\n    text\n, PRIMARY KEY(pack, recno)\n);<\/code><\/pre>\n<p>\nTipi\u010dna tak\u0161na tabela (\u017ee sekcionirana, seveda, zato je to - predloga sekcije), kjer je najpomembnej\u0161e - besedilo. V\u010dasih kar obse\u017eno.<\/p>\n<p>Ne pozabimo, da \u201efizi\u010dna\u201c velikost enega zapisa v PG ne more biti ve\u010dja od ene podatkovne strani, a \u201elogi\u010dna\u201c velikost - to je neka druga zgodba. Za zapis obse\u017enih vrednosti v polje (varchar\/text\/bytea) se uporablja <noindex><a rel=\"nofollow\" href=\"https:\/\/postgrespro.ru\/docs\/postgresql\/12\/storage-toast\">tehnologija TOAST<\/a><\/noindex>:<\/p>\n<blockquote><p>PostgreSQL uporablja fiksno velikost strani (obi\u010dajno 8 KB) in ne dovoljuje, da k tuples zavzamejo ve\u010d strani. Zato ni mogo\u010de neposredno shraniti zelo velikih vrednosti polj. Da bi premagali to omejitev, se velike vrednosti polj stisnejo in\/ali razdelijo na ve\u010d fizi\u010dnih vrstic. To se dogaja neopazno za uporabnika in ima majhen vpliv na ve\u010dino stre\u017eni\u0161ke kode. Ta metoda je znana kot TOAST \u2026<\/p><\/blockquote>\n<p>\nDejansko se za vsako tabelo z \"potencialno velikimi\" polji samodejno <noindex><a rel=\"nofollow\" href=\"https:\/\/postgrespro.ru\/docs\/postgresql\/12\/storage-toast#STORAGE-TOAST-ONDISK\">ustvari parna tabela z \"rezanjem\"<\/a><\/noindex> vsake \"velike\" vnose na segmente po 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>\nTorej, \u010de imamo za zapisati vrstico z \"veliko\" vrednostjo <code>data<\/code>, se dejansko zapisovanje zgodi <b>ne samo v glavno tabelo in njen PK, temve\u010d tudi v TOAST in njen PK<\/b>.<\/p>\n<h4>Zmanj\u0161ujemo vpliv TOAST<\/h4>\n<p>\nToda ve\u010dina vnosov kljub temu ni tako velika, <b>v 8KB bi se morala prilegati<\/b> \u2014 kako pri tem prihraniti?..<\/p>\n<p>Tu nam pride v pomo\u010d atribut <noindex><a rel=\"nofollow\" href=\"https:\/\/postgrespro.ru\/docs\/postgresql\/12\/storage-toast#STORAGE-TOAST-ONDISK\"><code>STORAGE<\/code><\/a><\/noindex> pri stolpcu tabele:<\/p>\n<blockquote>\n<ul>\n<li><b>EXTENDED<\/b> dovoli tako stiskanje kot tudi lo\u010deno shranjevanje. To <b>je standardna mo\u017enost<\/b> za ve\u010dino tipov podatkov, zdru\u017eljivih s TOAST. Najprej se posku\u0161a izvesti stiskanje, nato pa se shrani izven tabele, \u010de je vrstica \u0161e vedno prevelika.<\/li>\n<li><b>MAIN<\/b> dovoli stiskanje, vendar ne lo\u010denega shranjevanja. (Dejansko bo lo\u010deno shranjevanje v tem primeru izvedeno za tak\u0161ne stolpce, ampak le <b>kot skrajna re\u0161itev<\/b>, ko ni druge mo\u017enosti za zmanj\u0161anje vrstice, da bi se prilegala na stran.)<\/li>\n<\/ul>\n<\/blockquote>\n<p>Dejansko to\u010dno to potrebujemo za besedilo \u2014 <b>maksimalno stisniti, in \u010de ne gre nikakor \u2014 prenesti v TOAST<\/b>. To lahko storimo kar \"v \u017eivo\", z enim ukazom:<\/p>\n<pre><code class=\"sql\">ALTER TABLE rawdata_orig ALTER COLUMN data SET STORAGE MAIN;<\/code><\/pre>\n<p><\/p>\n<h4>Kako oceniti u\u010dinek<\/h4>\n<p>\nKer se vsak dan pretok podatkov spreminja, ne moremo primerjati absolutnih \u0161tevilk, toda v relativnih je <b>manj\u0161i dele\u017e<\/b> zapisali v TOAST \u2014 tem bolje. Toda tukaj je nevarnost \u2014 \u010dim ve\u010dji je \"fizi\u010dni\" obseg vsakega posameznega vnosa, tem \"\u0161ir\u0161i\" postane indeks, ker mora pokriti ve\u010dje \u0161tevilo podatkovnih strani.<\/p>\n<p>Oddelek <b>pred spremembami<\/b>:<\/p>\n<pre><code class=\"plaintext\">heap  = 37GB (39%)\nTOAST = 54GB (57%)\nPK    =  4GB ( 4%)\n<\/code><\/pre>\n<p>\nOddelek <b>po spremembah<\/b>:<\/p>\n<pre><code class=\"plaintext\">heap  = 37GB (67%)\nTOAST = 16GB (29%)\nPK    =  2GB ( 4%)<\/code><\/pre>\n<p>\nDejansko smo <b>za\u010deli zapisovati v TOAST dvakrat redkeje<\/b>, kar je olaj\u0161alo ne le disk, ampak tudi CPU:<\/p>\n<p><img decoding=\"async\" alt=\"\u0160tedimo malo novca 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 malo novca na velikim koli\u010dinama u PostgreSQL-u\" src=\"\/wp-content\/uploads\/2020\/04\/6bd3b18146c20959693f961e41fff447.jpg\" style=\"display:block;margin: 0 auto;\" \/><br \/>\nOpazil bom, da smo 'brali' disk manj, ne le 'pisali' - saj je pri vstavljanju zapisov v katero koli tabelo potrebno 'prebrati' tudi del drevesa vsakega od indeksov, da bi dolo\u010dili njegovo prihodnjo pozicijo v njih.<\/p>\n<h2>Komu je na PostgreSQL 11 lepo<\/h2>\n<p>\nPo nadgradnji na PG11 smo se odlo\u010dili nadaljevati s 'fine-tuningom' TOAST in opazili, da je od te razli\u010dice naprej na voljo parameter za nastavitev <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>Koda za obdelavo TOAST se aktivira le, \u010de je velikost niza, ki ga je treba shraniti v tabeli, ve\u010dja od TOAST_TUPLE_THRESHOLD bajtov (obi\u010dajno 2 Kb). Koda TOAST bo stiskala in\/ali prena\u0161ala vrednosti polja izven tabele, dokler velikost niza ne bo manj\u0161a od TOAST_TUPLE_TARGET bajtov (spremenljiva velikost, obi\u010dajno tudi 2 Kb) ali dokler ne bo mogo\u010de zmanj\u0161ati obsega.<\/p><\/blockquote>\n<p>Odlo\u010dili smo se, da so na\u0161i podatki obi\u010dajno ali 'zelo kratki' ali 'zelo dolgi', zato smo se odlo\u010dili omejiti na najmanj\u0161o mo\u017eno vrednost:<\/p>\n<pre><code class=\"sql\">ALTER TABLE rawplan_orig SET (toast_tuple_target = 128);<\/code><\/pre>\n<p>\nPoglejmo, kako so nove nastavitve vplivale na obremenitev diska po ponastavitvi:<\/p>\n<p><img decoding=\"async\" alt=\"\u0160tedimo malo novca na velikim koli\u010dinama u PostgreSQL-u\" src=\"\/wp-content\/uploads\/2020\/04\/ccaa4879e413a566b362d01582eb8c19.jpg\" style=\"display:block;margin: 0 auto;\" \/><br \/>\nNe slabo! Povpre\u010dna <b>vrsta v vrsti do diska se je zmanj\u0161ala<\/b> pribli\u017eno 1,5-krat, medtem ko je 'zasedenost' diska padla za 20%! Morda pa je to na kak\u0161en na\u010din vplivalo na CPU?<\/p>\n<p><img decoding=\"async\" alt=\"\u0160tedimo malo novca na velikim koli\u010dinama u PostgreSQL-u\" src=\"\/wp-content\/uploads\/2020\/04\/f7026e5809853d35c6fb7a8376b9f369.jpg\" style=\"display:block;margin: 0 auto;\" \/><br \/>\nVsaj slab\u0161e zagotovo ni postalo. \u010ceprav je te\u017eko presoditi, \u010de tudi tak\u0161ne koli\u010dine \u0161e vedno ne morejo dvigniti povpre\u010dne obremenitve CPU nad <b>5%<\/b>.<\/p>\n<h2>Izmenjava mestne zneske\u2026 se spreminja!<\/h2>\n<p>\nKot je znano, peni var\u010duje rublje, in pri na\u0161ih shranjevanjih okoli <b>10TB\/mesec<\/b> tudi majhna optimizacija lahko prinese dober dobi\u010dek. Zato smo pozorni na fizi\u010dno strukturo svojih podatkov - kako to\u010dno <b>'so razporejeni' polja znotraj zapisa<\/b> vsake od tabel.<\/p>\n<p>Ker zaradi <noindex><a rel=\"nofollow\" href=\"https:\/\/habr.com\/ru\/company\/postgrespro\/blog\/444536\/\">poravnave podatkov<\/a><\/noindex> to neposredno <noindex><a rel=\"nofollow\" href=\"https:\/\/docs.gitlab.com\/ee\/development\/ordering_table_columns.html\">vpliva na rezultatni volumen<\/a><\/noindex>:<\/p>\n<blockquote><p>\u0160tevilne arhitekture predvidevajo poravnavo podatkov na mejah strojnih besed. Na primer, na 32-bitnem sistemu x86 bodo celi \u0161tevili (tip integer, zasede 4 bajte) poravnani na meji 4-bajtnih besed, prav tako kot \u0161tevila z dvojno natan\u010dnostjo (tip double precision, 8 bajtov). Na 64-bitnem sistemu bodo vrednosti double poravnane na meji 8-bajtnih besed. To je \u0161e en razlog za nezdru\u017eljivost.<\/p>\n<p>Zaradi poravnanja, velikost tabelarne vrstice je odvisna od vrstnega reda postavitve polj. Obi\u010dajno je ta u\u010dinek slabo opazen, vendar lahko v nekaterih primerih povzro\u010di znatno pove\u010danje velikosti. Na primer, \u010de me\u0161amo polja tipov char(1) in integer, bo med njimi praviloma 3 bajte izgubljenih.<\/p><\/blockquote>\n<p>\nZa\u010dnimo s sinteti\u010dnimi modeli:<\/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 bajtov\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 bajtov<\/code><\/pre>\n<p>\nOd kod so pri\u0161la dodatna dva bajta v prvem primeru? Preprosto \u2014 <b>2-bajtni smallint se poravna na 4-bajtno mejo<\/b> pred naslednjim poljem, medtem ko, ko je zadnji, ni ni\u010desar, kar bi se lahko poravnalo, in ni potrebe.<\/p>\n<p>V teoriji je vse dobro in lahko premikamo polja po \u017eelji. Poglejmo to na realnih podatkih, na primeru ene od tabel, katere dnevni odsek zaseda 10\u201315GB.<\/p>\n<p>Izvorna struktura:<\/p>\n<pre><code class=\"sql\">CREATE TABLE public.plan_20190220\n(\n-- Podedovano iz tabele plan:  pack uuid NOT NULL,\n-- Podedovano iz tabele plan:  recno smallint NOT NULL,\n-- Podedovano iz tabele plan:  host uuid,\n-- Podedovano iz tabele plan:  ts timestamp with time zone,\n-- Podedovano iz tabele plan:  exectime numeric(32,3),\n-- Podedovano iz tabele plan:  duration numeric(32,3),\n-- Podedovano iz tabele plan:  bufint bigint,\n-- Podedovano iz tabele plan:  bufmem bigint,\n-- Podedovano iz tabele plan:  bufdsk bigint,\n-- Podedovano iz tabele plan:  apn uuid,\n-- Podedovano iz tabele plan:  ptr uuid,\n-- Podedovano 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>\nOdsek po spremembi vrstnega reda stolpcev \u2014 enaki <b>isti polji, le druga\u010den vrstni red<\/b>:<\/p>\n<pre><code class=\"sql\">CREATE TABLE public.plan_20190221\n(\n-- Podedovano iz tabele plan:  dt date NOT NULL,\n-- Podedovano iz tabele plan:  ts timestamp with time zone,\n-- Podedovano iz tabele plan:  pack uuid NOT NULL,\n-- Podedovano iz tabele plan:  recno smallint NOT NULL,\n-- Podedovano iz tabele plan:  host uuid,\n-- Podedovano iz tabele plan:  apn uuid,\n-- Podedovano iz tabele plan:  ptr uuid,\n-- Podedovano iz tabele plan:  bufint bigint,\n-- Podedovano iz tabele plan:  bufmem bigint,\n-- Podedovano iz tabele plan:  bufdsk bigint,\n-- Podedovano iz tabele plan:  exectime numeric(32,3),\n-- Podedovano 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>\nSkupni obseg odseka se dolo\u010di s \u0161tevilom \u201edejstev\u201c in je odvisen le od zunanjih procesov, zato bomo delili velikost heap (<code>pg_relation_size<\/code>) we will get the number of records in it \u2014 that is, we will obtain <b>the average size of an actual stored record<\/b>:<\/p>\n<p><img decoding=\"async\" alt=\"\u0160tedimo malo novca 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% in volume<\/b>, great!<\/p>\n<p>But it\u2019s not all that rosy \u2014 after all, <b>we cannot change the order of fields in the indexes<\/b>, and therefore \"in general\" (<code>pg_total_relation_size<\/code>)\u2026<\/p>\n<p><img decoding=\"async\" alt=\"\u0160tedimo malo novca na velikim koli\u010dinama u PostgreSQL-u\" src=\"\/wp-content\/uploads\/2020\/04\/8beff38e5034fc0d40665b75cb3b3625.jpg\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n\u2026 still in this case <b>we saved 1.5%<\/b>, without changing any lines of code. Indeed!<\/p>\n<p><img decoding=\"async\" alt=\"\u0160tedimo malo novca na velikim koli\u010dinama u PostgreSQL-u\" src=\"\/wp-content\/uploads\/2020\/04\/10f4a2151465a38bf45823a5d360302b.jpg\" style=\"display:block;margin: 0 auto;\" \/><\/p>\n<p>I should note that the above arrangement of fields is not necessarily the most optimal. Because some blocks of fields we don\u2019t want to \"break apart\" for aesthetic reasons \u2014 for example, a pair <code>(pack, recno)<\/code>, which serves as the PK for this table.<\/p>\n<p>Overall, defining the \"minimal\" arrangement of fields is a fairly simple \"combinatorial\" task. So you may achieve even better results with your data than we did \u2014 give it a try!<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 - 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\/sl\/blog\/administrirovanie\/ekonomim-kopeechku-na-bolshih-obemah-v-postgresql\" \/>\n\t\t<meta name=\"generator\" content=\"All in One SEO (AIOSEO) 5.0.5\" \/>\n\t\t<meta property=\"og:locale\" content=\"sl_SI\" \/>\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\/sl\/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\udd47Saving a penny on large volumes in PostgreSQL | ProHoster","description":"Continuing the topic of recording large data streams raised in the previous article about partitioning, we will discuss the ways in which this can be done.","canonical_url":"https:\/\/prohoster.info\/sl\/blog\/administrirovanie\/ekonomim-kopeechku-na-bolshih-obemah-v-postgresql","robots":"max-image-preview:large","keywords":"","webmasterTools":{"miscellaneous":""},"schema":null,"og:locale":"sl_SI","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\/sl\/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\/sl\/wp-json\/wp\/v2\/posts\/79039","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/prohoster.info\/sl\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/prohoster.info\/sl\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/prohoster.info\/sl\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/prohoster.info\/sl\/wp-json\/wp\/v2\/comments?post=79039"}],"version-history":[{"count":0,"href":"https:\/\/prohoster.info\/sl\/wp-json\/wp\/v2\/posts\/79039\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/prohoster.info\/sl\/wp-json\/wp\/v2\/media\/79040"}],"wp:attachment":[{"href":"https:\/\/prohoster.info\/sl\/wp-json\/wp\/v2\/media?parent=79039"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/prohoster.info\/sl\/wp-json\/wp\/v2\/categories?post=79039"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/prohoster.info\/sl\/wp-json\/wp\/v2\/tags?post=79039"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}