{"id":79028,"date":"2020-04-23T19:43:19","date_gmt":"2020-04-23T17:43:19","guid":{"rendered":"https:\/\/prohoster.info\/blog\/administrirovanie\/pishem-v-postgresql-na-subsvetovoj-1-host-1-day-1tb"},"modified":"2020-04-23T19:43:19","modified_gmt":"2020-04-23T17:43:19","slug":"pishem-v-postgresql-na-subsvetovoj-1-host-1-day-1tb","status":"publish","type":"post","link":"https:\/\/prohoster.info\/no\/blog\/administrirovanie\/pishem-v-postgresql-na-subsvetovoj-1-host-1-day-1tb","title":{"rendered":"Skriver i PostgreSQL p\u00e5 lys\u00e5r: 1 vert, 1 dag, 1TB","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"<p>Nyleg fortalte jeg om hvordan man kan bruke standardoppskrifter <noindex><a rel=\"nofollow\" href=\"https:\/\/habr.com\/ru\/company\/tensor\/blog\/492694\/\">for \u00e5 \u00f8ke ytelsen til SQL-sp\u00f8rsm\u00e5l \"for lesing\"<\/a><\/noindex> fra PostgreSQL-database. I dag skal vi snakke om hvordan <b>man kan gj\u00f8re skrivingen<\/b> til DB mer effektiv uten \u00e5 bruke noen \"justeringer\" i konfigurasjonen \u2014 bare ved \u00e5 organisere datastreamene riktig.<\/p>\n<p><img decoding=\"async\" alt=\"Skriver i PostgreSQL p\u00e5 lys\u00e5r: 1 vert, 1 dag, 1TB\" src=\"\/wp-content\/uploads\/2020\/04\/cbebbe0ed0e9a6590a4e8dd144f82f40.jpg\" style=\"display:block;margin: 0 auto;\" \/><\/p>\n<h2>#1. \u0421\u0435\u043a\u0446\u0438\u043e\u043d\u0438\u0440\u043e\u0432\u0430\u043d\u0438\u0435<\/h2>\n<p>\nArtikkelen handler om hvordan og hvorfor man b\u00f8r organisere <noindex><a rel=\"nofollow\" href=\"https:\/\/habr.com\/ru\/post\/483170\/\">applikasjonssegregering \"i teorien\"<\/a><\/noindex> har allerede v\u00e6rt, her skal vi snakke om praktisk anvendelse av noen metoder innenfor v\u00e5r <noindex><a rel=\"nofollow\" href=\"https:\/\/habr.com\/ru\/post\/487380\/\">tjeneste for overv\u00e5king av hundrevis av PostgreSQL-servere<\/a><\/noindex>.<br \/>\n<noindex><a rel=\"nofollow\" name=\"habracut\"><\/a><\/noindex><\/p>\n<h4>\u00abGjerningar fr\u00e5 fortida\u2026\u00bb<\/h4>\n<p>\nOpprinnelig, som enhver MVP, startet prosjektet v\u00e5rt med en relativt liten belastning \u2014 overv\u00e5kningen ble bare utf\u00f8rt for et titalls kritiske servere, alle tabeller var relativt kompakte\u2026 Men tiden gikk, antallet overv\u00e5kede verter \u00f8kte, og da vi igjen pr\u00f8vde \u00e5 h\u00e5ndtere en av <b>tabellene med en st\u00f8rrelse p\u00e5 1,5 TB<\/b>, inns\u00e5 vi at selv om det var mulig \u00e5 leve slik, var det veldig ubeleilig.<\/p>\n<p>Tidene var nesten legendariske, ulike versjoner av PostgreSQL 9.x var aktuelle, s\u00e5 all sekregering m\u00e5tte gj\u00f8res \"manuelt\" \u2014 gjennom <b>arv fra tabeller og triggere<\/b> routing med dynamisk <code>EXECUTE<\/code>.<\/p>\n<p><img decoding=\"async\" alt=\"Skriver i PostgreSQL p\u00e5 lys\u00e5r: 1 vert, 1 dag, 1TB\" src=\"\/wp-content\/uploads\/2020\/04\/a480e75ccec73080aa2d0be1435d2a2e.jpg\" style=\"display:block;margin: 0 auto;\" \/><br \/>\nDen resulterende l\u00f8sningen viste seg \u00e5 v\u00e6re tilstrekkelig universell til at man kunne oversette den til alle tabeller:<\/p>\n<ul>\n<li>En tom \"header\"-foreldretabell ble erkl\u00e6rt, der alle <b>n\u00f8dvendige indekser og triggere ble beskrevet<\/b>.<\/li>\n<li>Skrivningen fra klientens synspunkt ble utf\u00f8rt i \"roottabellen\", mens inne i tabellen ble det brukt <b>routing-trigger<\/b> <code>F\u00d8R SETTING<\/code> opptak \u00abfysisk\u00bb vart sett inn i den n\u00f8dvendige seksjonen. Hvis det ikkje fanst ein slik enno \u2014 fanga vi eit unntak og\u2026<\/li>\n<li>\u2026 ved hjelp av <noindex><a rel=\"nofollow\" href=\"https:\/\/habr.com\/ru\/post\/492464\/\"><code>CREATE TABLE ... (LIKE ... INCLUDING ...)<\/code><\/a><\/noindex> ble det opprettet en <b>seksjon med begrensning p\u00e5 den n\u00f8dvendige datoen<\/b>, slik at ved datainnhenting ble lesingen utf\u00f8rt utelukkende i den.<\/li>\n<\/ul>\n<p><\/p>\n<h4>PG10: f\u00f8rste fors\u00f8k<\/h4>\n<p>\nMen sekregering via arv var historisk ikke spesielt tilpasset for arbeid med en aktiv skriving eller et stort antall sektioner-arvinger. For eksempel kan vi huske at algoritmen for valg av n\u00f8dvendig seksjon hadde <b>kvadratisk kompleksitet<\/b>, hvilket med 100+ seksjoner fungerer, som man forst\u00e5r...<\/p>\n<p>I PG10 ble denne situasjonen sterkt optimalisert ved \u00e5 implementere st\u00f8tte for <noindex><a rel=\"nofollow\" href=\"https:\/\/postgrespro.ru\/docs\/postgresql\/10\/ddl-partitioning\">innf\u00f8dt sekregering<\/a><\/noindex>. S\u00e5 vi pr\u00f8vde umiddelbart \u00e5 bruke det rett etter migreringen av lagringen, men\u2026<\/p>\n<p>Som det ble klart etter \u00e5 ha gr\u00e5tt i manualen, st\u00f8tter en naturlig partisjonert tabell i denne versjonen:<\/p>\n<ul>\n<li>ikke beskrivelse av indekser<\/li>\n<li>st\u00f8tter ikke triggere<\/li>\n<li>kan ikke v\u00e6re ingen 'etterkommer'<\/li>\n<li>st\u00f8tter ikke <code>INSERT ... ON CONFLICT<\/code><\/li>\n<li>kan ikke automatisk generere en seksjon<\/li>\n<\/ul>\n<p>\nVi fikk oss et skulderslag og inns\u00e5 at vi ikke kunne klare oss uten \u00e5 modifisere applikasjonen, og utsetter videre forskning i et halvt \u00e5r.<\/p>\n<h4>PG10: en ny sjanse<\/h4>\n<p>\nS\u00e5 vi begynte \u00e5 l\u00f8se de oppst\u00e5tte problemene en etter en:<\/p>\n<ol>\n<li>Siden triggere og <code>ON CONFLICT<\/code> ble vi \u00e5 finne dem n\u00f8dvendige noen steder, laget vi en mellomliggende <b>proxy-tabell<\/b>.<\/li>\n<li><b>Vi fjernet 'routingen'<\/b> i triggerne \u2014 det vil si <code>EXECUTE<\/code>.<\/li>\n<li>Vi tok ut <b>mal-tabellen med alle indeksene<\/b>, slik at de ikke engang var til stede i proxy-tabellen.<\/li>\n<\/ol>\n<p>\n<img decoding=\"async\" alt=\"Skriver i PostgreSQL p\u00e5 lys\u00e5r: 1 vert, 1 dag, 1TB\" src=\"\/wp-content\/uploads\/2020\/04\/db3118798357575568489f6b575373b6.jpg\" style=\"display:block;margin: 0 auto;\" \/><br \/>\nTil slutt, etter alt dette, ble hovedtabellen naturlig partisjonert. Opprettelsen av en ny seksjon forblir fortsatt p\u00e5 applikasjonens samvittighet.<\/p>\n<h4>Vi 'bearbeider' ordb\u00f8ker<\/h4>\n<p>\nSom i ethvert analysesystem, hadde vi ogs\u00e5 <b>fakta og skj\u00e6ringspunkter<\/b> (ordb\u00f8ker). I v\u00e5rt tilfelle, fungerte for eksempel <noindex><a rel=\"nofollow\" href=\"https:\/\/youtu.be\/5XKbFb-l5Do?t=2487\">kroppen av 'malen'<\/a><\/noindex> av ensartede langsomme foresp\u00f8rselen eller teksten i selve foresp\u00f8rselen.<\/p>\n<p>Faktaene v\u00e5re hadde v\u00e6rt partisjonert etter dager lenge, s\u00e5 vi fjernet trygt utdaterte seksjoner, og de plaget oss ikke (loggene da!). Men ordb\u00f8ker ble et problem\u2026<\/p>\n<p>Det kan ikke sies at de var veldig mange, men omtrent <b>for 100TB 'fakta' fikk vi et ordbok p\u00e5 2,5TB.<\/b>. Fra en slik tabell er det praktisk talt umulig \u00e5 slette noe, \u00e5 komprimere den for rimelig tid, og skriving til den ble gradvis mer og mer tidkrevende.<\/p>\n<p>Det virker som en ordbok\u2026 hver oppf\u00f8ring m\u00e5 v\u00e6re representert n\u00f8yaktig \u00e9n gang\u2026 og det er riktig, men!.. Ingen hindrer oss i \u00e5 ha <b>en egen ordbok for hver dag<\/b>! Ja, det gir en viss overfl\u00f8dighet, men tillater:<\/p>\n<ul>\n<li><b>\u00e5 skrive\/lese raskere<\/b> p\u00e5 grunn av mindre st\u00f8rrelse p\u00e5 seksjonen<\/li>\n<li><b>\u00e5 bruke mindre minne<\/b> p\u00e5 grunn av arbeid med mer kompakte indekser<\/li>\n<li><b>\u00e5 lagre mindre data<\/b> p\u00e5 grunn av muligheten til raskt \u00e5 slette utdaterte<\/li>\n<\/ul>\n<p>\nSom et resultat av hele tiltaket <b>falt CPU-belastningen med ~30%, og diskbelastningen med ~50%<\/b>:<\/p>\n<p><img decoding=\"async\" alt=\"Skriver i PostgreSQL p\u00e5 lys\u00e5r: 1 vert, 1 dag, 1TB\" src=\"\/wp-content\/uploads\/2020\/04\/fd3a219a304dc46173a7eb435502fe02.jpg\" style=\"display:block;margin: 0 auto;\" \/><br \/>\nSamtidig fortsatte vi \u00e5 skrive inn i databasen n\u00f8yaktig det samme, bare med mindre belastning.<\/p>\n<h2>#2. \u042d\u0432\u043e\u043b\u044e\u0446\u0438\u044f \u0438 \u0440\u0435\u0444\u0430\u043a\u0442\u043e\u0440\u0438\u043d\u0433 \u0411\u0414<\/h2>\n<p>\nS\u00e5 vi stoppet p\u00e5 det punktet at vi har <b>en seksjon for hver dag<\/b> med data. Egenspeiset, <code>CHECK (dt = '2018-10-12'::date)<\/code> \u2014 og det er n\u00f8kkelen til partisjonering og betingelsen for at en post havner i en bestemt seksjon.<\/p>\n<p>Siden alle rapporter i tjenesten v\u00e5r er bygget p\u00e5 spesifikke datoer, har ogs\u00e5 indeksene fra \"de ikke-partisjonerte tidene\" alltid v\u00e6rt av typen <i>(Server, <b>Dato<\/b>, Planmal)<\/i>, <i>(Server, <b>Dato<\/b>, PlanNode)<\/i>, <i>(<b>Dato<\/b>, Feilklasse, Server)<\/i>,\u2026<\/p>\n<p>Men n\u00e5 lever <u>hver av disse seksjonene<\/u> med sine egne instanser <u>av hver slik indeks\u2026 Og innen hver seksjon<\/u>datoen er en konstant <b>\u2026 Det viser seg at vi n\u00e5 skriver inn konstanten<\/b> som et av feltene, noe som \u00f8ker b\u00e5de volumet og s\u00f8ketiden, men gir ingen resultater. Vi har lagt ut feller for oss selv, ups\u2026<\/p>\n<p><img decoding=\"async\" alt=\"Skriver i PostgreSQL p\u00e5 lys\u00e5r: 1 vert, 1 dag, 1TB\" src=\"\/wp-content\/uploads\/2020\/04\/c7644644b960c568c4adaeec57cfef2d.jpg\" style=\"display:block;margin: 0 auto;\" \/><br \/>\nRetningen for optimalisering er \u00e5penbar \u2014 bare <b>fjerne dato-feltet fra alle indekser<\/b> p\u00e5 partisjonerte tabeller. Med v\u00e5re volumer er gevinsten rundt <b>1 TB\/uke<\/b>!<\/p>\n<p>Og n\u00e5 la oss merke at denne terabyte m\u00e5tte ogs\u00e5 skrives p\u00e5 en eller annen m\u00e5te. Det vil si at vi n\u00e5 m\u00e5 <b>belaste disken mindre<\/b>! P\u00e5 dette bildet er effekten av rensingen vi viet en uke til godt synlig:<\/p>\n<p><img decoding=\"async\" alt=\"Skriver i PostgreSQL p\u00e5 lys\u00e5r: 1 vert, 1 dag, 1TB\" src=\"\/wp-content\/uploads\/2020\/04\/f45e3b26337074a07751ea28961009bf.jpg\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<\/p>\n<h2>#3. \u00ab\u0420\u0430\u0437\u043c\u0430\u0437\u044b\u0432\u0430\u0435\u043c\u00bb \u043f\u0438\u043a\u043e\u0432\u0443\u044e \u043d\u0430\u0433\u0440\u0443\u0437\u043a\u0443<\/h2>\n<p>\nEn av de store utfordringene med tunge systemer er <b>overfl\u00f8dig synkronisering<\/b> av operasjoner som ikke krever det. Noen ganger \u00abfordi vi ikke la merke til det\u00bb, noen ganger \u00abfordi det var enklere\u00bb, men f\u00f8r eller senere m\u00e5 vi bli kvitt det.<\/p>\n<p>Vi forst\u00f8rrer forrige bilde \u2014 og ser at disken v\u00e5r <b>\u00abhenter\u00bb med dobbel amplitude<\/b> mellom nabom\u00e5lingene, noe som \u00e5penbart \u00abstatistisk\u00bb ikke burde v\u00e6re ved s\u00e5 mange operasjoner:<\/p>\n<p><img decoding=\"async\" alt=\"Skriver i PostgreSQL p\u00e5 lys\u00e5r: 1 vert, 1 dag, 1TB\" src=\"\/wp-content\/uploads\/2020\/04\/ac3f19213cba0f111864c6dbf9a73912.jpg\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<br \/>\nDet er ganske enkelt \u00e5 oppn\u00e5. Vi hadde allerede <b>nesten 1000 servere<\/b>, hver behandles av en egen logisk str\u00f8m, og hver str\u00f8m slipper den akkumulerte informasjonen for \u00e5 sende til databasen med en bestemt periode, omtrent s\u00e5nn:<\/p>\n<pre><code class=\"javascript\">setInterval(sendToDB, interval)<\/code><\/pre>\n<p>\nProblemet ligger n\u00f8yaktig i det at <b>alle str\u00f8mmer starter omtrent samtidig<\/b>, derfor tidspunktet for sendingen deres nesten alltid sammenfaller \u00abtil punktet\u00bb. Ups nr. 2\u2026<\/p>\n<p>Heldigvis er dette ganske lett \u00e5 fikse, <b>ved \u00e5 legge til \u00abtilfeldig\u00bb spredning<\/b> over tid:<\/p>\n<pre><code class=\"javascript\">setInterval(sendToDB, interval * (1 + 0.1 * (Math.random() - 0.5)))<\/code><\/pre>\n<p><\/p>\n<h2>#4. \u041a\u044d\u0448\u0438\u0440\u0443\u0435\u043c, \u0447\u0442\u043e \u043d\u0443\u0436\u043d\u043e \u043c\u043e\u0436\u043d\u043e<\/h2>\n<p>\nDet tredje tradisjonelle problemet med highload \u2014 <b>mangel p\u00e5 cache<\/b> der det <i>skulle kunna<\/i> m\u00e5 v\u00e6re.<\/p>\n<p>For example, we have implemented the ability to analyze by nodes of the plan (all these <code>Seq Scan on users<\/code>), but to immediately think that they are, in bulk, the same \u2014 is a mistake.<\/p>\n<p>No, of course, nothing is written back to the database, this filters the trigger with <code>INSERT ... ON CONFLICT DO NOTHING<\/code>. But still, this data reaches the database, and there\u2019s also unnecessary <b>reading for conflict checking<\/b> that has to be done. Oops \u21163\u2026<\/p>\n<p>The difference in the number of records sent to the database before\/after caching is enabled \u2014 is obvious:<\/p>\n<p><img decoding=\"async\" alt=\"Skriver i PostgreSQL p\u00e5 lys\u00e5r: 1 vert, 1 dag, 1TB\" src=\"\/wp-content\/uploads\/2020\/04\/37fa7e64a674f03a79f2765a79ec8138.jpg\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<br \/>\nAnd this is the accompanying drop in storage load:<\/p>\n<p><img decoding=\"async\" alt=\"Skriver i PostgreSQL p\u00e5 lys\u00e5r: 1 vert, 1 dag, 1TB\" src=\"\/wp-content\/uploads\/2020\/04\/b2c563b4b41755211e77768d80f8702f.jpg\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<\/p>\n<h2>Totalt<\/h2>\n<p>\n\"Terabyte-per-day\" may sound frightening. If you do everything correctly, it's just <b>2^40 bytes \/ 86400 seconds = ~12.5MB\/s<\/b>, which even desktop IDE drives could handle. \ud83d\ude42<\/p>\n<p>And seriously, even with a tenfold \"skew\" in load over the day, you can easily stay within the capabilities of modern SSDs.<\/p>\n<p><img decoding=\"async\" alt=\"Skriver i PostgreSQL p\u00e5 lys\u00e5r: 1 vert, 1 dag, 1TB\" src=\"\/wp-content\/uploads\/2020\/04\/6f3f8d4636ba50f3d5401bf4e456757f.jpg\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<br \/>Kilde: <a content=\"nofollow\" rel=\"nofollow\" href=\"https:\/\/habr.com\/ru\/post\/497008\/\">habr.com<\/a> <\/p>","protected":false,"gt_translate_keys":[{"key":"rendered","format":"html"}]},"excerpt":{"rendered":"<p>\u041d\u0435\u0434\u0430\u0432\u043d\u043e \u044f \u0440\u0430\u0441\u0441\u043a\u0430\u0437\u0430\u043b, \u043a\u0430\u043a \u0441 \u043f\u043e\u043c\u043e\u0449\u044c\u044e \u0442\u0438\u043f\u043e\u0432\u044b\u0445 \u0440\u0435\u0446\u0435\u043f\u0442\u043e\u0432 \u0443\u0432\u0435\u043b\u0438\u0447\u0438\u0442\u044c \u043f\u0440\u043e\u0438\u0437\u0432\u043e\u0434\u0438\u0442\u0435\u043b\u044c\u043d\u043e\u0441\u0442\u044c SQL-\u0437\u0430\u043f\u0440\u043e\u0441\u043e\u0432 \u00ab\u043d\u0430 \u0447\u0442\u0435\u043d\u0438\u0435\u00bb \u0438\u0437 PostgreSQL-\u0431\u0430\u0437\u044b. \u0421\u0435\u0433\u043e\u0434\u043d\u044f \u0436\u0435 \u0440\u0435\u0447\u044c \u043f\u043e\u0439\u0434\u0435\u0442 \u043e \u0442\u043e\u043c, \u043a\u0430\u043a \u043c\u043e\u0436\u043d\u043e \u0441\u0434\u0435\u043b\u0430\u0442\u044c \u0431\u043e\u043b\u0435\u0435 \u044d\u0444\u0444\u0435\u043a\u0442\u0438\u0432\u043d\u043e\u0439 \u0437\u0430\u043f\u0438\u0441\u044c \u0432 \u0411\u0414 \u0431\u0435\u0437 \u0438\u0441\u043f\u043e\u043b\u044c\u0437\u043e\u0432\u0430\u043d\u0438\u044f \u043a\u0430\u043a\u0438\u0445-\u043b\u0438\u0431\u043e \u00ab\u043a\u0440\u0443\u0442\u0438\u043b\u043e\u043a\u00bb \u0432 \u043a\u043e\u043d\u0444\u0438\u0433\u0435 \u2014 \u043f\u0440\u043e\u0441\u0442\u043e \u043f\u0440\u0430\u0432\u0438\u043b\u044c\u043d\u043e \u043e\u0440\u0433\u0430\u043d\u0438\u0437\u043e\u0432\u0430\u0432 \u043f\u043e\u0442\u043e\u043a\u0438 \u0434\u0430\u043d\u043d\u044b\u0445. #1. \u0421\u0435\u043a\u0446\u0438\u043e\u043d\u0438\u0440\u043e\u0432\u0430\u043d\u0438\u0435 \u0421\u0442\u0430\u0442\u044c\u044f \u043f\u0440\u043e \u0442\u043e, \u043a\u0430\u043a \u0438 \u0437\u0430\u0447\u0435\u043c \u0441\u0442\u043e\u0438\u0442 \u043e\u0440\u0433\u0430\u043d\u0438\u0437\u043e\u0432\u044b\u0432\u0430\u0442\u044c \u043f\u0440\u0438\u043a\u043b\u0430\u0434\u043d\u043e\u0435 \u0441\u0435\u043a\u0446\u0438\u043e\u043d\u0438\u0440\u043e\u0432\u0430\u043d\u0438\u0435 \u00ab\u0432 \u0442\u0435\u043e\u0440\u0438\u0438\u00bb [&hellip;]<\/p>\n","protected":false,"gt_translate_keys":[{"key":"rendered","format":"html"}]},"author":1,"featured_media":79029,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[688],"tags":[],"class_list":["post-79028","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=\"\u041d\u0435\u0434\u0430\u0432\u043d\u043e \u044f \u0440\u0430\u0441\u0441\u043a\u0430\u0437\u0430\u043b, \u043a\u0430\u043a \u0441 \u043f\u043e\u043c\u043e\u0449\u044c\u044e \u0442\u0438\u043f\u043e\u0432\u044b\u0445 \u0440\u0435\u0446\u0435\u043f\u0442\u043e\u0432 \u0443\u0432\u0435\u043b\u0438\u0447\u0438\u0442\u044c \u043f\u0440\u043e\u0438\u0437\u0432\u043e\u0434\u0438\u0442\u0435\u043b\u044c\u043d\u043e\u0441\u0442\u044c SQL-\u0437\u0430\u043f\u0440\u043e\u0441\u043e\u0432 \u00ab\u043d\u0430 \u0447\u0442\u0435\u043d\u0438\u0435\u00bb \u0438\u0437.\" \/>\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\/no\/blog\/administrirovanie\/pishem-v-postgresql-na-subsvetovoj-1-host-1-day-1tb\" \/>\n\t\t<meta name=\"generator\" content=\"All in One SEO (AIOSEO) 5.0.5.1\" \/>\n\t\t<meta property=\"og:locale\" content=\"nn_NO\" \/>\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\u041f\u0438\u0448\u0435\u043c \u0432 PostgreSQL \u043d\u0430 \u0441\u0443\u0431\u0441\u0432\u0435\u0442\u043e\u0432\u043e\u0439: 1 host, 1 day, 1TB | ProHoster\" \/>\n\t\t<meta property=\"og:description\" content=\"\u041d\u0435\u0434\u0430\u0432\u043d\u043e \u044f \u0440\u0430\u0441\u0441\u043a\u0430\u0437\u0430\u043b, \u043a\u0430\u043a \u0441 \u043f\u043e\u043c\u043e\u0449\u044c\u044e \u0442\u0438\u043f\u043e\u0432\u044b\u0445 \u0440\u0435\u0446\u0435\u043f\u0442\u043e\u0432 \u0443\u0432\u0435\u043b\u0438\u0447\u0438\u0442\u044c \u043f\u0440\u043e\u0438\u0437\u0432\u043e\u0434\u0438\u0442\u0435\u043b\u044c\u043d\u043e\u0441\u0442\u044c SQL-\u0437\u0430\u043f\u0440\u043e\u0441\u043e\u0432 \u00ab\u043d\u0430 \u0447\u0442\u0435\u043d\u0438\u0435\u00bb \u0438\u0437.\" \/>\n\t\t<meta property=\"og:url\" content=\"https:\/\/prohoster.info\/no\/blog\/administrirovanie\/pishem-v-postgresql-na-subsvetovoj-1-host-1-day-1tb\" \/>\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:19+00:00\" \/>\n\t\t<meta property=\"article:modified_time\" content=\"2020-04-23T17:43:19+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\udd47Writing in PostgreSQL at light speed: 1 host, 1 day, 1TB | ProHoster","description":"Recently, I discussed how to use typical recipes to increase the performance of \"read\" SQL queries.","canonical_url":"https:\/\/prohoster.info\/no\/blog\/administrirovanie\/pishem-v-postgresql-na-subsvetovoj-1-host-1-day-1tb","robots":"max-image-preview:large","keywords":"","webmasterTools":{"miscellaneous":""},"schema":null,"og:locale":"nn_NO","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\u041f\u0438\u0448\u0435\u043c \u0432 PostgreSQL \u043d\u0430 \u0441\u0443\u0431\u0441\u0432\u0435\u0442\u043e\u0432\u043e\u0439: 1 host, 1 day, 1TB | ProHoster","og:description":"\u041d\u0435\u0434\u0430\u0432\u043d\u043e \u044f \u0440\u0430\u0441\u0441\u043a\u0430\u0437\u0430\u043b, \u043a\u0430\u043a \u0441 \u043f\u043e\u043c\u043e\u0449\u044c\u044e \u0442\u0438\u043f\u043e\u0432\u044b\u0445 \u0440\u0435\u0446\u0435\u043f\u0442\u043e\u0432 \u0443\u0432\u0435\u043b\u0438\u0447\u0438\u0442\u044c \u043f\u0440\u043e\u0438\u0437\u0432\u043e\u0434\u0438\u0442\u0435\u043b\u044c\u043d\u043e\u0441\u0442\u044c SQL-\u0437\u0430\u043f\u0440\u043e\u0441\u043e\u0432 \u00ab\u043d\u0430 \u0447\u0442\u0435\u043d\u0438\u0435\u00bb \u0438\u0437.","og:url":"https:\/\/prohoster.info\/no\/blog\/administrirovanie\/pishem-v-postgresql-na-subsvetovoj-1-host-1-day-1tb","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:19+00:00","article:modified_time":"2020-04-23T17:43:19+00:00","article:publisher":"https:\/\/www.facebook.com\/prohoster","article:author":"https:\/\/www.facebook.com\/prohoster"},"aioseo_meta_data":{"post_id":"79028","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:34","updated":"2022-10-01 20:30:41","focus_keyword":null,"additional_keywords":null,"truseo_locale":null},"gt_translate_keys":[{"key":"link","format":"url"}],"_links":{"self":[{"href":"https:\/\/prohoster.info\/no\/wp-json\/wp\/v2\/posts\/79028","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/prohoster.info\/no\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/prohoster.info\/no\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/prohoster.info\/no\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/prohoster.info\/no\/wp-json\/wp\/v2\/comments?post=79028"}],"version-history":[{"count":0,"href":"https:\/\/prohoster.info\/no\/wp-json\/wp\/v2\/posts\/79028\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/prohoster.info\/no\/wp-json\/wp\/v2\/media\/79029"}],"wp:attachment":[{"href":"https:\/\/prohoster.info\/no\/wp-json\/wp\/v2\/media?parent=79028"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/prohoster.info\/no\/wp-json\/wp\/v2\/categories?post=79028"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/prohoster.info\/no\/wp-json\/wp\/v2\/tags?post=79028"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}