{"id":31905,"date":"2019-10-31T21:43:52","date_gmt":"2019-10-31T18:43:52","guid":{"rendered":"https:\/\/prohoster.info\/blog\/happy-party-ili-para-strok-vospominanij-o-znakomstve-s-sektsionirovaniem-v-postgresql10\/"},"modified":"2019-10-31T21:43:52","modified_gmt":"2019-10-31T18:43:52","slug":"happy-party-ili-para-strok-vospominanij-o-znakomstve-s-sektsionirovaniem-v-postgresql10","status":"publish","type":"post","link":"https:\/\/prohoster.info\/sk\/blog\/administrirovanie\/happy-party-ili-para-strok-vospominanij-o-znakomstve-s-sektsionirovaniem-v-postgresql10","title":{"rendered":"\u0160\u0165astn\u00e1 p\u00e1rty alebo p\u00e1r riadkov spomienok na obozn\u00e1menie sa so sekcionovan\u00edm v PostgreSQL10","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"

Predslov alebo ako vznikla my\u0161lienka sekcionovania<\/h4>\n

\nZa\u010diatok pr\u00edbehu je tu: Pam\u00e4t\u00e1\u0161 si, ako to cel\u00e9 za\u010dalo. V\u0161etko bolo prv\u00fdkr\u00e1t a znova.<\/a><\/noindex> Potom, \u010do boli takmer v\u0161etky zdroje na optimaliz\u00e1ciu dopytu, v tom \u010dase, vy\u010derpan\u00e9, sa objavila ot\u00e1zka \u2014 a \u010do \u010falej? Tak sa zrodila my\u0161lienka o sekcionovan\u00ed. <\/p>\n

\"\u0160\u0165astn\u00e1
\n
\nLyrick\u00e9 odbo\u010denie:<\/b>
\nPresne 'v tom momente', preto\u017ee ako sa uk\u00e1zalo, existovali nevyu\u017eit\u00e9 rezervy na optimaliz\u00e1ciu<\/a><\/noindex>. \u010eakujem asmm<\/a><\/noindex> a Habr !<\/i><\/p>\n

Tak\u017ee, ako e\u0161te m\u00f4\u017eete spravi\u0165 z\u00e1kazn\u00edka akoby \u0161\u0165astn\u00fdm a z\u00e1rove\u0148 si zlep\u0161i\u0165 svoje zru\u010dnosti? <\/p>\n

Ak to v\u0161etko maxim\u00e1lne zjednodu\u0161\u00edme<\/b>, tak, mo\u017enost\u00ed, ako nie\u010do radik\u00e1lne zlep\u0161i\u0165 v r\u00fdchlosti datab\u00e1zy, je len nieko\u013eko:
\n1) Extern\u00fd sp\u00f4sob \u2014 zvy\u0161ujeme zdroje, men\u00edme konfigur\u00e1ciu;
\n2) Intenz\u00edvny sp\u00f4sob \u2014 optimaliz\u00e1cia dopytov<\/p>\n

Preto, opakujem, v tom \u010dase u\u017e nebolo jasn\u00e9, \u010do e\u0161te zmeni\u0165 v dopyte na ur\u00fdchlenie, bola zvolen\u00e1 cesta \u2014 zmien dizajnu tabuliek.<\/b><\/p>\n

Tak\u017ee \u2014 vznik\u00e1 hlavn\u00e1 ot\u00e1zka \u2014 \u010do a ako budeme meni\u0165? <\/b>
\n<\/a><\/noindex><\/p>\n

Po\u010diato\u010dn\u00e9 podmienky<\/h2>\n

\nPo prv\u00e9, existuje tak\u00e1to ERD (zobrazen\u00e9 podmiene\u010dne jednoducho):
\n\"\u0160\u0165astn\u00e1
\nHlavn\u00e9 vlastnosti:<\/p>\n

    \n
  1. vz\u0165ahy \u201emnoho k mnoh\u00fdm\u201c<\/li>\n
  2. tabu\u013eka u\u017e m\u00e1 potenci\u00e1lny k\u013e\u00fa\u010d na sekcionovanie <\/li>\n<\/ol>\n

    Po\u010diato\u010dn\u00fd dopyt:<\/p>\n

    SELECT\n            p.\"PARAMETER_ID\" as  parameter_id,\n            pc.\"PC_NAME\" AS pc_name,\n            pc.\"CUSTOMER_PARTNUMBER\" AS customer_partnumber,\n            w.\"LASERMARK\" AS lasermark,\n            w.\"LOTID\" AS lotid,\n            w.\"REPORTED_VALUE\" AS reported_value,\n            w.\"LOWER_SPEC_LIMIT\" AS lower_spec_limit,\n            w.\"UPPER_SPEC_LIMIT\" AS upper_spec_limit,\n            p.\"TYPE_CALCUL\" AS type_calcul,\n            s.\"SHIPMENT_NAME\" AS shipment_name,\n            s.\"SHIPMENT_DATE\" AS shipment_date,\n            extract(year from s.\"SHIPMENT_DATE\") AS year,\n            extract(month from s.\"SHIPMENT_DATE\") as month,\n            s.\"REPORT_NAME\" AS report_name,\n            p.\"SPARAM_NAME\" AS SPARAM_name,\n            p.\"CUSTOMERPARAM_NAME\" AS customerparam_name\n        FROM data w INNER JOIN shipment s ON s.\"SHIPMENT_ID\" = w.\"SHIPMENT_ID\"\n             INNER JOIN parameters p ON p.\"PARAMETER_ID\" = w.\"PARAMETER_ID\"\n             INNER JOIN shipment_pc sp ON s.\"SHIPMENT_ID\" = sp.\"SHIPMENT_ID\"\n             INNER JOIN pc pc ON pc.\"PC_ID\" = sp.\"PC_ID\"\n             INNER JOIN ( SELECT w2.\"LASERMARK\" , MAX(s2.\"SHIPMENT_DATE\") AS \"SHIPMENT_DATE\"\n                          FROM shipment s2 INNER JOIN data w2 ON s2.\"SHIPMENT_ID\" = w2.\"SHIPMENT_ID\" \n                          GROUP BY w2.\"LASERMARK\"\n                         ) md ON md.\"SHIPMENT_DATE\" = s.\"SHIPMENT_DATE\" AND md.\"LASERMARK\" = w.\"LASERMARK\"\n        WHERE \n             s.\"SHIPMENT_DATE\" >= '2018-07-01' AND s.\"SHIPMENT_DATE\" <= '2018-09-30' ;\n<\/code><\/pre>\n
    \nV\u00fdsledky vykonania na testovacej datab\u00e1ze:<\/b>
    \nN\u00e1klady <\/b>: 502 997.55
    \n\u010cas vykonania<\/b>: 505 sek\u00fand.<\/p>\n
    \u010co vid\u00edme? Be\u017en\u00fd dotaz na \u010dasovom reze. 
    \nRob\u00edme najjednoduch\u0161ie logick\u00e9 predpoklady: ak existuje v\u00fdber \u010dasov\u00e9ho rezu, pom\u00f4\u017ee n\u00e1m? Spr\u00e1vne \u2014 sekcionovanie.<\/p>\n
    \u010co sekcionova\u0165?<\/h2>\n
    \nNa prv\u00fd poh\u013ead je v\u00fdber zrejm\u00fd \u2014 deklarat\u00edvne sekcionovanie tabu\u013eky \u201eshipment\u201c pod\u013ea k\u013e\u00fa\u010da \u201eSHIPMENT_DATE\u201c (prebiehaj\u00fac ve\u013emi dopredu \u2014 nakoniec v produkcii to bolo trochu inak<\/i>). <\/p>\n
    Ako sekcionova\u0165?<\/h2>\n
    \nT\u00fato ot\u00e1zku nie je pr\u00edli\u0161 \u0165a\u017ek\u00e9 zodpoveda\u0165. Navy\u0161e, v PostgreSQL 10 je teraz priate\u013esk\u00fd mechanizmus sekcionovania. 
    \nTak\u017ee: <\/p>\n
      \n
    1.  Ulo\u017e\u00edme dump p\u00f4vodnej tabu\u013eky \u2014 pg_dump source_table<\/i><\/li>\n
    2.  Odstr\u00e1nime p\u00f4vodn\u00fa tabu\u013eku \u2014 drop table source_table<\/i><\/li>\n
    3. Vytvor\u00edme rodi\u010dovsk\u00fa tabu\u013eku so sekcionovan\u00edm pod\u013ea rozsahu \u2014 create table source_table<\/i><\/li>\n
    4.  Vytvor\u00edme sekcie \u2014 create table source_table, create index<\/i><\/li>\n
    5.  Importujeme dump vytvoren\u00fd v kroku 1 \u2014 pg_restore<\/i><\/li>\n<\/ol>\n
      <\/p>\n
      Skripty pre sekcionovanie <\/h2>\n
      \nPre jednoduchos\u0165 a pohodlie boli kroky 2,3,4 zjednoten\u00e9 do jedn\u00e9ho skriptu. <\/p>\n
      Tak\u017ee: 
      \nUlo\u017e\u00edme dump p\u00f4vodnej tabu\u013eky<\/b><\/p>\n
      pg_dump postgres --file=\\\/dump\\\/shipment.dmp --format=c --table=shipment --verbose > \\\/dump\\\/shipment.log 2>&1<\/code><\/pre>\n
      \nOdstr\u00e1nime p\u00f4vodn\u00fa tabu\u013eku + Vytvor\u00edme rodi\u010dovsk\u00fa tabu\u013eku so sekcionovan\u00edm pod\u013ea rozsahu + Vytvor\u00edme sekcie<\/b><\/p>\n
      --create_partition_shipment.sql\ndo language plpgsql $$\ndeclare \nrec_shipment_date RECORD ;\npartition_name varchar;\nindex_name varchar;\ncurrent_year varchar ;\ncurrent_month varchar ;\nbegin_year varchar ;\nbegin_month varchar ;\nnext_year varchar ;\nnext_month varchar ;\nfirst_flag boolean ;\ni integer ;\nbegin\n  RAISE NOTICE 'VYTV\u00c1\u0158ENIE DO\u010cASN\u00c9 TABU\u013dKY PRE D\u00c1TUM DODANIA';\n  CREATE TEMP TABLE tmp_shipment_date as select distinct \"SHIPMENT_DATE\" from shipment order by \"SHIPMENT_DATE\" ;\n\n  RAISE NOTICE 'ODSTRA\u0147TE TABU\u013dKU shipment';\n  drop table shipment cascade ;\n  \n  CREATE TABLE public.shipment\n  (\n    \"SHIPMENT_ID\" integer NOT NULL DEFAULT nextval('shipment_shipment_id_seq'::regclass),\n    \"SHIPMENT_NAME\" character varying(30) COLLATE pg_catalog.\"default\",\n    \"SHIPMENT_DATE\" timestamp without time zone,\n    \"REPORT_NAME\" character varying(40) COLLATE pg_catalog.\"default\"\n  )\n  PARTITION BY RANGE (\"SHIPMENT_DATE\")\n  WITH (\n      OIDS = FALSE\n  )\n  TABLESPACE pg_default;\n\n  RAISE NOTICE 'TVORBA PART\u00cdCI\u00cd PRE TABU\u013dKU shipment';\n\n  current_year:='0';\n  current_month:='0';\n\n  begin_year := '0' ;\n  begin_month := '0'  ;\n  next_year := '0' ;\n  next_month := '0'  ;\n\n  FOR rec_shipment_date IN SELECT * FROM tmp_shipment_date LOOP\n      \n      RAISE NOTICE 'SHIPMENT_DATE=%',rec_shipment_date.\"SHIPMENT_DATE\";\n      \n      current_year := date_part('year' ,rec_shipment_date.\"SHIPMENT_DATE\");\n      current_month := date_part('month' ,rec_shipment_date.\"SHIPMENT_DATE\") ; \n\n      IF to_number(current_month,'99') = to_date( begin_year||'.'||begin_month, 'YYYY.MM') AND \n         to_date( current_year||'.'||current_month, 'YYYY.MM') < to_date( next_year||'.'||next_month, 'YYYY.MM') AND \n         NOT first_flag \n      THEN\n         CONTINUE ; \n      ELSE\n       --NOV\u00c9 hranice iba pre druh\u00fd a \u010fal\u0161\u00edkr\u00e1t \n       begin_year := current_year ;\n       begin_month := current_month ;   \n   \n        IF current_month = '12' THEN\n          next_year := date_part('year' ,rec_shipment_date."SHIPMENT_DATE" + interval '1 year') ;\n        ELSE\n          next_year := current_year ;\n        END IF;\n     \n       next_month := date_part('month' ,rec_shipment_date."SHIPMENT_DATE" + interval '1 month') ;\n\n      END IF;      \n\n      partition_name := 'shipment_shipment_date_'||begin_year||'-'||begin_month||'-01-'|| next_year||'-'||next_month||'-01'  ;\n \n     EXECUTE format('CREATE TABLE ' || quote_ident(partition_name) || ' PARTITION OF shipment FOR VALUES FROM ( %L ) TO ( %L )  ' , current_year||'-'||current_month||'-01' , next_year||'-'||next_month||'-01'  ) ; \n\n      index_name := partition_name||'_shipment_id_idx';\n      RAISE NOTICE 'N\u00c1ZOV INDEXU =%',index_name;\n      EXECUTE format('CREATE INDEX ' || quote_ident(index_name) || ' ON '|| quote_ident(partition_name) ||' USING btree ("SHIPMENT_ID") TABLESPACE pg_default ' ) ; \n\n      --Zru\u0161i\u0165 vlajku prv\u00e9ho \u010dasu\n      first_flag := false ;\n   \n  END LOOP;\n\nend\n$$;<\/code><\/pre>\n
      \nImportujeme dump<\/b><\/p>\n
      pg_restore -d postgres --data-only --format=c --table=shipment --verbose  shipment.dmp > \/tmp\/data_dump\/shipment_restore.log 2>&1<\/code><\/pre>\n
      <\/p>\n
      Kontrolujeme v\u00fdsledky sekvenovania<\/h2>\n
      \n\u010co teda m\u00e1me ako v\u00fdsledok? \u00dapln\u00fd text pl\u00e1nu vykonania je dlh\u00fd a nudn\u00fd, a preto sta\u010d\u00ed obmedzi\u0165 sa na kone\u010dn\u00e9 \u010d\u00edsla.<\/p>\n
      Bolo<\/h3>\n
      \nN\u00e1klady:<\/b> 502 997.55
      \n\u010cas vykonania:<\/b> 505 sek\u00fand.<\/p>\n
      Stalo<\/h3>\n
      \nN\u00e1klady:<\/b> 77 872.36
      \n\u010cas vykonania:<\/b> 79 sek\u00fand.<\/p>\n
      Celkom dobr\u00fd v\u00fdsledok. Zn\u00ed\u017eili sme n\u00e1klady a \u010das vykonania. Tak\u017ee pou\u017e\u00edvanie sekcionovania prin\u00e1\u0161a o\u010dak\u00e1van\u00fd efekt a celkovo \u2014 bez prekvapen\u00ed. <\/p>\n
      Pote\u0161i\u0165 z\u00e1kazn\u00edka<\/h2>\n
      \nV\u00fdsledky testovania boli predlo\u017een\u00e9 z\u00e1kazn\u00edkovi na pos\u00fadenie. A po obozn\u00e1men\u00ed im bol vydan\u00fd nieko\u013eko prekvapiv\u00fd verdikt: \u201eVynikaj\u00faco, sekcionujte tabu\u013eku \u201adata\u2018.\u201c<\/p>\n
      \u00c1no, ale my sme sk\u00famali \u00faplne in\u00fa tabu\u013eku \u201ashipment\u2018, tabu\u013eka \u201adata\u2018 nem\u00e1 pole \u201aSHIPMENT_DATE\u2018.<\/p>\n
      Nie je probl\u00e9m, prid\u00e1vajte, men\u0165e. Hlavn\u00e9 je, aby z\u00e1kazn\u00edka uspokojilo, \u010do v\u00fdsledok prinesie, detaily realiz\u00e1cie nie s\u00fa a\u017e tak d\u00f4le\u017eit\u00e9.<\/p>\n
      Sekcionujeme hlavn\u00fa tabu\u013eku \u201adata\u2018<\/h2>\n
      \nV podstate nevznikli \u017eiadne zvl\u00e1\u0161tne \u0165a\u017ekosti. Aj ke\u010f sa algoritmus sekcionovania s\u00edce trochu zmenil.<\/p>\n
      Prid\u00e1vame st\u013apec \u201aSHIPMENT_DATA\u2018 do tabu\u013eky \u201adata\u2018<\/b><\/p>\n
      psql -h host -U datab\u00e1za -d u\u017e\u00edvate\u013e\n=> ALTER TABLE data ADD COLUMN \"SHIPMENT_DATE\" timestamp without time zone ;<\/code><\/pre>\n
      Vypln\u00edme hodnoty st\u013apca \u201aSHIPMENT_DATA\u2018 v tabu\u013eke \u201adata\u2018 hodnotami rovnomenn\u00e9ho st\u013apca z tabu\u013eky \u201ashipment\u2018<\/b><\/p>\n
      -----------------------------\n--update_data.sql\n--aktualiz\u00e1cia pre upraven\u00fa tabu\u013eku \u201adata\u2018 na hodnoty \u201ashipment_data\u2018 z tabu\u013eky \u201ashipment\u2018\n--verzia 1.0\ndo language plpgsql $$\ndeclare \nrec_shipment_data RECORD ;\nshipment_date timestamp without time zone ; \nrow_count integer ;\ntotal_rows integer ;\nbegin\n\n  select count(*) into total_rows from shipment ; \n  RAISE NOTICE 'Celkov\u00fd %',total_rows;\n  row_count:= 0 ;\n\n  FOR rec_shipment_data IN SELECT * FROM shipment LOOP\n\n   update data set \"SHIPMENT_DATE\" = rec_shipment_data.\"SHIPMENT_DATE\" where \"SHIPMENT_ID\" = rec_shipment_data.\"SHIPMENT_ID\";\n   \n   row_count:=  row_count +1 ;\n   RAISE NOTICE 'po\u010det riadkov = % , z %',row_count,total_rows;\n  END LOOP;\n\nend\n$$;<\/code><\/pre>\n
      \nUklad\u00e1me dump tabu\u013eky \u201adata\u2018<\/b><\/p>\n
      pg_dump postgres --file=\\\/dump\\\/data.dmp --format=c --table=data --verbose > \\\/dump\\\/data.log 2>&1<\\\/source<\/code><\/pre>\n
      Znovu vytv\u00e1rame sekcionovan\u00fa tabu\u013eku \u201adata\u2018<\/b><\/p>\n
      --create_partition_data.sql\n--vytvori\u0165 partition pre tabu\u013eku \"wafer data\" pod\u013ea rozsahu st\u013apca \"shipment_data\" s trvan\u00edm jeden mesiac\n--verzia 1.0\ndo language plpgsql $$\ndeclare \nrec_shipment_date RECORD ;\npartition_name varchar;\nindex_name varchar;\ncurrent_year varchar ;\ncurrent_month varchar ;\nbegin_year varchar ;\nbegin_month varchar ;\nnext_year varchar ;\nnext_month varchar ;\nfirst_flag boolean ;\ni integer ;\n\nbegin\n\n  RAISE NOTICE 'VYTVORTE DO\u010cASN\u00da TABU\u013dKU PRE SHIPMENT_DATE';\n  CREATE TEMP TABLE tmp_shipment_date as select distinct \"SHIPMENT_DATE\" from shipment order by \"SHIPMENT_DATE\" ;\n\n  RAISE NOTICE 'ZMAZA\u0164 TABU\u013dKU data';\n  drop table data cascade ;\n\n  RAISE NOTICE 'VYTVORI\u0164 PARTITIONOVAN\u00da TABU\u013dKU data';\n  \n  CREATE TABLE public.data\n  (\n    \"RUN_ID\" integer,\n    \"LASERMARK\" character varying(20) COLLATE pg_catalog.\"default\" NOT NULL,\n    \"LOTID\" character varying(80) COLLATE pg_catalog.\"default\",\n    \"SHIPMENT_ID\" integer NOT NULL,\n    \"PARAMETER_ID\" integer NOT NULL,\n    \"INTERNAL_VALUE\" character varying(75) COLLATE pg_catalog.\"default\",\n    \"REPORTED_VALUE\" character varying(75) COLLATE pg_catalog.\"default\",\n    \"LOWER_SPEC_LIMIT\" numeric,\n    \"UPPER_SPEC_LIMIT\" numeric , \n    \"SHIPMENT_DATE\" timestamp without time zone\n  )\n  PARTITION BY RANGE (\"SHIPMENT_DATE\")\n  WITH (\n    OIDS = FALSE\n  )\n  TABLESPACE pg_default ;\n\n  RAISE NOTICE 'VYTVORI\u0164 PART\u00cdCIE PRE TABU\u013dKU data';\n\n  current_year:='0';\n  current_month:='0';\n\n  begin_year := '0' ;\n  begin_month := '0'  ;\n  next_year := '0' ;\n  next_month := '0'  ;\n  i := 1;\n\n  FOR rec_shipment_date IN SELECT * FROM tmp_shipment_date LOOP\n      \n      RAISE NOTICE 'SHIPMENT_DATE=%',rec_shipment_date.\"SHIPMENT_DATE\";\n      \n      current_year := date_part('year' ,rec_shipment_date.\"SHIPMENT_DATE\");\n      current_month := date_part('month' ,rec_shipment_date.\"SHIPMENT_DATE\") ; \n\n      --Inicializova\u0165 hranice\n      IF   begin_year = '0' THEN\n       RAISE NOTICE '***Inicializova\u0165 hranice';\n       first_flag := true ; --prv\u00fdkr\u00e1t flag\n       begin_year := current_year ;\n       begin_month := current_month ;   \n   \n        IF current_month = '12' THEN\n          next_year := date_part('year' ,rec_shipment_date.\"SHIPMENT_DATE\" + interval '1 year') ;\n        ELSE\n          next_year := current_year ;\n        END IF;\n     \n       next_month := date_part('month' ,rec_shipment_date.\"SHIPMENT_DATE\" + interval '1 month') ;\n\n      END IF;\n\n      RAISE NOTICE 'Aktu\u00e1lne d\u00e1ta = %',to_char( to_date( current_year||'.'||current_month, 'YYYY.MM'), 'YYYY.MM');\n      RAISE NOTICE 'Za\u010d\u00ednaj\u00face d\u00e1ta = %',to_char( to_date( begin_year||'.'||begin_month, 'YYYY.MM'), 'YYYY.MM');\n      RAISE NOTICE '\u010eal\u0161ie d\u00e1ta = %',to_char( to_date( next_year||'.'||next_month, 'YYYY.MM'), 'YYYY.MM');\n\n      IF to_date( current_year||'.'||current_month, 'YYYY.MM') >= to_date( begin_year||'.'||begin_month, 'YYYY.MM') AND \n         to_date( current_year||'.'||current_month, 'YYYY.MM') < to_date( next_year||'.'||next_month, 'YYYY.MM') AND \n         NOT first_flag \n      THEN\n         RAISE NOTICE '***POKRA\u010cOVA\u0164';\n         CONTINUE ; \n      ELSE\n       --NOV\u00c9 hranice len pre druh\u00fd a \u010fal\u0161\u00edkr\u00e1t \n       RAISE NOTICE '***NOV\u00c9 HRANICE';\n       begin_year := current_year ;\n       begin_month := current_month ;   \n   \n        IF current_month = '12' THEN\n          next_year := date_part('year' ,rec_shipment_date."SHIPMENT_DATE" + interval '1 year') ;\n        ELSE\n          next_year := current_year ;\n        END IF;\n     \n       next_month := date_part('month' ,rec_shipment_date."SHIPMENT_DATE" + interval '1 month') ;\n\n      END IF;      \n\n      IF to_number(current_month,'99') < 10 THEN\n        current_month := '0'||current_month ; \n      END IF ;\n\n      IF to_number(begin_month,'99') < 10 THEN\n        begin_month := '0'||begin_month ; \n      END IF ;\n\n      IF to_number(next_month,'99') < 10 THEN\n        next_month := '0'||next_month ; \n      END IF ;\n\n      RAISE NOTICE 'current_year=% , current_month=% ',current_year,current_month;\n      RAISE NOTICE 'begin_year=% , begin_month=% ',begin_year,begin_month;\n      RAISE NOTICE 'next_year=% , next_month=% ',next_year,next_month;\n\n      partition_name := 'data_'||begin_year||begin_month||'01_'||next_year||next_month||'01'  ;\n\n      RAISE NOTICE '\u010c\u00cdSLO PART\u00cdCIE % , N\u00c1ZOV TABU\u013dKY =%',i , partition_name;\n      \n      EXECUTE format('VYTVORI\u0164 TABU\u013dKU ' || quote_ident(partition_name) || ' PARTITION OF data FOR VALUES FROM ( %L ) TO ( %L )  ' , begin_year||'-'||begin_month||'-01' , next_year||'-'||next_month||'-01'  ) ; \n\n      index_name := partition_name||'_shipment_id_parameter_id_idx';\n      RAISE NOTICE 'N\u00c1ZOV INDEXU =%',index_name;\n      EXECUTE format('VYTVORI\u0164 INDEX ' || quote_ident(index_name) || ' ON '|| quote_ident(partition_name) ||' USING btree ("SHIPMENT_ID", "PARAMETER_ID") TABLESPACE pg_default ' ) ; \n\n      index_name := partition_name||'_lasermark_idx';\n      RAISE NOTICE 'N\u00c1ZOV INDEXU =%',index_name;\n      EXECUTE format('VYTVORI\u0164 INDEX ' || quote_ident(index_name) || ' ON '|| quote_ident(partition_name) ||' USING btree ("LASERMARK" COLLATE pg_catalog."default") TABLESPACE pg_default ' ) ; \n\n      index_name := partition_name||'_shipment_id_idx';\n      RAISE NOTICE 'N\u00c1ZOV INDEXU =%',index_name;\n      EXECUTE format('VYTVORI\u0164 INDEX ' || quote_ident(index_name) || ' ON '|| quote_ident(partition_name) ||' USING btree ("SHIPMENT_ID") TABLESPACE pg_default ' ) ; \n\n      index_name := partition_name||'_parameter_id_idx';\n      RAISE NOTICE 'N\u00c1ZOV INDEXU =%',index_name;\n      EXECUTE format('VYTVORI\u0164 INDEX ' || quote_ident(index_name) || ' ON '|| quote_ident(partition_name) ||' USING btree ("PARAMETER_ID") TABLESPACE pg_default ' ) ; \n\n      index_name := partition_name||'_shipment_date_idx';\n      RAISE NOTICE 'N\u00c1ZOV INDEXU =%',index_name;\n      EXECUTE format('VYTVORI\u0164 INDEX ' || quote_ident(index_name) || ' ON '|| quote_ident(partition_name) ||' USING btree ("SHIPMENT_DATE") TABLESPACE pg_default ' ) ; \n\n      --Zru\u0161i\u0165 prv\u00fdkr\u00e1t flag\n      first_flag := false ;\n\n  END LOOP;\nend\n$$;\n<\/code><\/pre>\n
      \nNahr\u00e1vame dump vytvoren\u00fd v kroku 3.<\/b><\/p>\n
      pg_restore -h host -u\u017e\u00edvate\u013e -d datab\u00e1za --data-only --format=c --table=data --verbose data.dmp > data_restore.log 2>&1<\/code><\/pre>\n
      \nVytv\u00e1rame samostatn\u00fa sekciu pre star\u00e9 \u00fadaje<\/b><\/p>\n
      ---------------------------------------------------\n--create_partition_for_old_dates.sql\n--vytvori\u0165 oddiely na uchov\u00e1vanie star\u00fdch d\u00e1t\n--verzia 1.0\ndo language plpgsql $$\ndeclare\nrec_shipment_date RECORD;\npartition_name varchar;\nindex_name varchar;\n\nbegin\n\n      SELECT min(\"SHIPMENT_DATE\") AS min_date INTO rec_shipment_date from data;\n\n      RAISE NOTICE 'Star\u00fd d\u00e1tum je %', rec_shipment_date.min_date;\n\n      partition_name := 'data_old_dates';\n\n      RAISE NOTICE 'N\u00c1ZOV ODDIELU JE %', partition_name;\n\n      EXECUTE format('CREATE TABLE ' || quote_ident(partition_name) || ' PARTITION OF data FOR VALUES FROM ( %L ) TO ( %L )  ', '1900-01-01',\n              to_char(rec_shipment_date.min_date, 'YYYY') || '-' || to_char(rec_shipment_date.min_date, 'MM') || '-01');\n\n      index_name := partition_name || '_shipment_id_parameter_id_idx';\n      EXECUTE format('CREATE INDEX ' || quote_ident(index_name) || ' ON ' || quote_ident(partition_name) || ' USING btree (\"SHIPMENT_ID\", \"PARAMETER_ID\") TABLESPACE pg_default');\n\n      index_name := partition_name || '_lasermark_idx';\n      EXECUTE format('CREATE INDEX ' || quote_ident(index_name) || ' ON ' || quote_ident(partition_name) || ' USING btree (\"LASERMARK\" COLLATE pg_catalog.\"default\") TABLESPACE pg_default');\n\n      index_name := partition_name || '_shipment_id_idx';\n      EXECUTE format('CREATE INDEX ' || quote_ident(index_name) || ' ON ' || quote_ident(partition_name) || ' USING btree (\"SHIPMENT_ID\") TABLESPACE pg_default');\n\n      index_name := partition_name || '_parameter_id_idx';\n      EXECUTE format('CREATE INDEX ' || quote_ident(index_name) || ' ON ' || quote_ident(partition_name) || ' USING btree (\"PARAMETER_ID\") TABLESPACE pg_default');\n\n      index_name := partition_name || '_shipment_date_idx';\n      EXECUTE format('CREATE INDEX ' || quote_ident(index_name) || ' ON ' || quote_ident(partition_name) || ' USING btree (\"SHIPMENT_DATE\") TABLESPACE pg_default');\n\nend\n$$;<\/code><\/pre>\n
      Kone\u010dn\u00e9 v\u00fdsledky:<\/h3>\n
      \nBolo<\/b>
      \nN\u00e1klady:<\/b> 502 997.55
      \n\u010cas vykonania<\/b>: 505 sek\u00fand.<\/p>\n
      Stalo<\/b>
      \nN\u00e1klady:<\/b> 68 533.70
      \n\u010cas vykonania:<\/b> 69 sek\u00fand<\/p>\n
      Zasl\u00fa\u017een\u00e9, \u00faplne zasl\u00fa\u017een\u00e9. A vzh\u013eadom na to, \u017ee sa po ceste podarilo aspo\u0148 trocha zvl\u00e1dnu\u0165 mechanizmus rozdelenia v PostgreSQL 10 \u2014 Skvel\u00fd v\u00fdsledok.<\/p>\n
      Lyrick\u00e9 odbo\u010denie<\/h2>\n
      \nA m\u00f4\u017ee by\u0165 e\u0161te lep\u0161ie \u2014 \u00c1NO, M\u00d4\u017dE!<\/b>Na to potrebujeme pou\u017ei\u0165 MATERIALIZED VIEW.
      \nCREATE MATERIALIZED VIEW LASERMARK_VIEW<\/b><\/p>\n
      CREATE MATERIALIZED VIEW LASERMARK_VIEW\nAS\nSELECT w.\"LASERMARK\", MAX(s.\"SHIPMENT_DATE\") AS \"SHIPMENT_DATE\"\nFROM shipment s INNER JOIN data w ON s.\"SHIPMENT_ID\" = w.\"SHIPMENT_ID\"\nGROUP BY w.\"LASERMARK\";\n\nCREATE INDEX lasermark_vw_shipment_date_ind on lasermark_view USING btree (\"SHIPMENT_DATE\") TABLESPACE pg_default;\nanalyze lasermark_view;\n<\/code><\/pre>\n
      \nOp\u00e4\u0165 prepisujeme dotaz:
      \nDotaz s vyu\u017eit\u00edm materialized view<\/b><\/p>\n
      VYBERTE\n            p.\"PARAMETER_ID\" ako parameter_id,\n            pc.\"PC_NAME\" ako pc_name,\n            pc.\"CUSTOMER_PARTNUMBER\" ako customer_partnumber,\n            w.\"LASERMARK\" ako lasermark,\n            w.\"LOTID\" ako lotid,\n            w.\"REPORTED_VALUE\" ako reported_value,\n            w.\"LOWER_SPEC_LIMIT\" ako lower_spec_limit,\n            w.\"UPPER_SPEC_LIMIT\" ako upper_spec_limit,\n            p.\"TYPE_CALCUL\" ako type_calcul,\n            s.\"SHIPMENT_NAME\" ako shipment_name,\n            s.\"SHIPMENT_DATE\" ako shipment_date,\n            extract(year from s.\"SHIPMENT_DATE\") ako year,\n            extract(month from s.\"SHIPMENT_DATE\") ako month,\n            s.\"REPORT_NAME\" ako report_name,\n            p.\"STC_NAME\" ako STC_name,\n            p.\"CUSTOMERPARAM_NAME\" ako customerparam_name\n        Z data w INNER JOIN shipment s NA s.\"SHIPMENT_ID\" = w.\"SHIPMENT_ID\"\n             INNER JOIN parameters p NA p.\"PARAMETER_ID\" = w.\"PARAMETER_ID\"\n             INNER JOIN shipment_pc sp NA s.\"SHIPMENT_ID\" = sp.\"SHIPMENT_ID\"\n             INNER JOIN pc pc NA pc.\"PC_ID\" = sp.\"PC_ID\"\n             INNER JOIN LASERMARK_VIEW md NA md.\"SHIPMENT_DATE\" = s.\"SHIPMENT_DATE\" A md.\"LASERMARK\" = w.\"LASERMARK\"\n        KDE\n              s.\"SHIPMENT_DATE\" >= '2018-07-01' A s.\"SHIPMENT_DATE\" <= '2018-09-30';\n<\/code><\/pre>\n
      \nA dost\u00e1vame \u010fal\u0161\u00ed v\u00fdsledok:<\/b>
      \nBolo<\/b>
      \nN\u00e1klady:<\/b> 502 997.55
      \n\u010cas vykonania<\/b>: 505 sek\u00fand<\/p>\n
      Stalo<\/b>
      \nN\u00e1klady:<\/b> 42 481.16
      \n\u010cas vykonania:<\/b> 43 sekundy.<\/p>\n
      Hoci samozrejme, tak pr\u00eds\u013eubn\u00fd v\u00fdsledok je zav\u00e1dzaj\u00faci, predstavy treba obnovi\u0165. Tak\u017ee kone\u010dn\u00fd \u010das na z\u00edskanie d\u00e1t predsa len ve\u013emi nepom\u00f4\u017ee. Ale ako experiment je to celkom zauj\u00edmav\u00e9.<\/p>\n
      V skuto\u010dnosti sa uk\u00e1zalo, \u017ee e\u0161te raz \u010fakujem asmm<\/a><\/noindex> a Habr-u !- dotaz mo\u017eno e\u0161te vylep\u0161i\u0165. <\/a><\/noindex><\/p>\n
      P\u00f3sledok<\/h2>\n
      \nTak\u017ee, z\u00e1kazn\u00edk je spokojn\u00fd. A je potrebn\u00e9 <\/b>vyu\u017ei\u0165 situ\u00e1ciu. <\/p>\n
      Nov\u00e1 \u00faloha<\/b>: \u010co mo\u017eno vymyslie\u0165, aby sme sa preh\u013abili a roz\u0161\u00edrili?<\/p>\n
      A tu si spom\u00ednam \u2014 chlapci, ve\u010f nem\u00e1me monitorovanie na\u0161ich datab\u00e1z PostgreSQL.<\/p>\n
      S r\u00fak na srdce, nejak\u00e9 monitorovanie vo forme Cloud Watch na AWS predsa len existuje. Ale ak\u00fd zmysel m\u00e1 toto monitorovanie pre DBA? V podstate \u017eiadny.<\/p>\n
      Ak sa naskytla \u0161anca urobi\u0165 nie\u010do u\u017eito\u010dn\u00e9 a zauj\u00edmav\u00e9 aj pre seba, nem\u00f4\u017ee\u0161 tak\u00fato \u0161ancu nevyu\u017ei\u0165 \u2026
      \nPRETO
      \n<\/b>
      \n\"\u0160\u0165astn\u00e1
      \n
      \nTakto sme sa dostali k najzauj\u00edmavej\u0161iemu:<\/p>\n
      3. decembra 2018.<\/b>
      \nRozhodnutie o za\u010diatku pr\u00e1c na presk\u00faman\u00ed dostupn\u00fdch mo\u017enost\u00ed monitorovania v\u00fdkonu dopytov PostgreSQL.\n<\/p><\/blockquote>\n
      Ale to u\u017e je \u00faplne in\u00fd pr\u00edbeh.<\/b><\/p>\n
      Pokra\u010dovanie, nasleduje\u2026<\/i>
      \n
      Zdroj:       habr.com<\/a><\/p>","protected":false,"gt_translate_keys":[{"key":"rendered","format":"html"}]},"excerpt":{"rendered":"
      \u041f\u0440\u0435\u0434\u0438\u0441\u043b\u043e\u0432\u0438\u0435 \u0438\u043b\u0438 \u043a\u0430\u043a \u0432\u043e\u0437\u043d\u0438\u043a\u043b\u0430 \u0438\u0434\u0435\u044f \u0441\u0435\u043a\u0446\u0438\u043e\u043d\u0438\u0440\u043e\u0432\u0430\u043d\u0438\u044f \u041d\u0430\u0447\u0430\u043b\u043e \u0438\u0441\u0442\u043e\u0440\u0438\u0438 \u0437\u0434\u0435\u0441\u044c: \u0422\u044b \u043f\u043e\u043c\u043d\u0438\u0448\u044c, \u043a\u0430\u043a \u0432\u0441\u0435 \u043d\u0430\u0447\u0438\u043d\u0430\u043b\u043e\u0441\u044c. \u0412\u0441\u0435 \u0431\u044b\u043b\u043e \u0432\u043f\u0435\u0440\u0432\u044b\u0435 \u0438 \u0432\u043d\u043e\u0432\u044c. \u041f\u043e\u0441\u043b\u0435 \u0442\u043e\u0433\u043e, \u043a\u0430\u043a \u043f\u043e\u0447\u0442\u0438 \u0432\u0441\u0435 \u0440\u0435\u0441\u0443\u0440\u0441\u044b \u0434\u043b\u044f \u043e\u043f\u0442\u0438\u043c\u0438\u0437\u0430\u0446\u0438\u0438 \u0437\u0430\u043f\u0440\u043e\u0441\u0430, \u043d\u0430 \u0442\u043e\u0442 \u043c\u043e\u043c\u0435\u043d\u0442, \u0431\u044b\u043b\u0438 \u0438\u0441\u0447\u0435\u0440\u043f\u0430\u043d\u044b, \u0432\u0441\u0442\u0430\u043b \u0432\u043e\u043f\u0440\u043e\u0441 \u2014 \u0430 \u0447\u0442\u043e \u0436\u0435 \u0434\u0430\u043b\u044c\u0448\u0435? \u0422\u0430\u043a \u0438 \u0432\u043e\u0437\u043d\u0438\u043a\u043b\u0430 \u0438\u0434\u0435\u044f \u043e \u0441\u0435\u043a\u0446\u0438\u043e\u043d\u0438\u0440\u043e\u0432\u0430\u043d\u0438\u0438. \u041b\u0438\u0440\u0438\u0447\u0435\u0441\u043a\u043e\u0435 \u043e\u0442\u0441\u0442\u0443\u043f\u043b\u0435\u043d\u0438\u0435: \u0418\u043c\u0435\u043d\u043d\u043e ‘\u043d\u0430 \u0442\u043e\u0442 \u043c\u043e\u043c\u0435\u043d\u0442’, \u043f\u043e\u0442\u043e\u043c\u0443, \u0447\u0442\u043e \u043a\u0430\u043a […]<\/p>\n","protected":false,"gt_translate_keys":[{"key":"rendered","format":"html"}]},"author":1,"featured_media":23765,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[688],"tags":[],"class_list":["post-31905","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-administrirovanie"],"aioseo_notices":[],"aioseo_head":"\n\t\t\n\t\n\t\n\t\n\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\n","aioseo_head_json":{"title":"\ud83e\udd47Happy Party alebo p\u00e1r riadkov spomienok na zozn\u00e1menie sa so sekcionovan\u00edm v PostgreSQL10 | ProHoster","description":"Predslov alebo ako vznikla my\u0161lienka sekcionovania Za\u010diatok pr\u00edbehu je tu: Pam\u00e4t\u00e1\u0161 si, ako to cel\u00e9 za\u010dalo.","canonical_url":"https:\/\/prohoster.info\/sk\/blog\/administrirovanie\/happy-party-ili-para-strok-vospominanij-o-znakomstve-s-sektsionirovaniem-v-postgresql10","robots":"max-image-preview:large","keywords":"","webmasterTools":{"miscellaneous":""},"schema":null,"og:locale":"sk_SK","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\udd47Happy Party \u0438\u043b\u0438 \u043f\u0430\u0440\u0430 \u0441\u0442\u0440\u043e\u043a-\u0432\u043e\u0441\u043f\u043e\u043c\u0438\u043d\u0430\u043d\u0438\u0439 \u043e \u0437\u043d\u0430\u043a\u043e\u043c\u0441\u0442\u0432\u0435 \u0441 \u0441\u0435\u043a\u0446\u0438\u043e\u043d\u0438\u0440\u043e\u0432\u0430\u043d\u0438\u0435\u043c \u0432 PostgreSQL10 | ProHoster","og:description":"\u041f\u0440\u0435\u0434\u0438\u0441\u043b\u043e\u0432\u0438\u0435 \u0438\u043b\u0438 \u043a\u0430\u043a \u0432\u043e\u0437\u043d\u0438\u043a\u043b\u0430 \u0438\u0434\u0435\u044f \u0441\u0435\u043a\u0446\u0438\u043e\u043d\u0438\u0440\u043e\u0432\u0430\u043d\u0438\u044f \u041d\u0430\u0447\u0430\u043b\u043e \u0438\u0441\u0442\u043e\u0440\u0438\u0438 \u0437\u0434\u0435\u0441\u044c: \u0422\u044b \u043f\u043e\u043c\u043d\u0438\u0448\u044c, \u043a\u0430\u043a \u0432\u0441\u0435 \u043d\u0430\u0447\u0438\u043d\u0430\u043b\u043e\u0441\u044c.","og:url":"https:\/\/prohoster.info\/sk\/blog\/administrirovanie\/happy-party-ili-para-strok-vospominanij-o-znakomstve-s-sektsionirovaniem-v-postgresql10","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-10-31T18:43:52+00:00","article:modified_time":"2019-10-31T18:43:52+00:00","article:publisher":"https:\/\/www.facebook.com\/prohoster","article:author":"https:\/\/www.facebook.com\/prohoster"},"aioseo_meta_data":{"post_id":"31905","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-21 08:22:19","breadcrumb_settings":null,"limit_modified_date":false,"reviewed_by":null,"ai":null,"created":"2021-03-01 03:09:25","updated":"2026-01-21 08:22:19","focus_keyword":null,"additional_keywords":null,"truseo_locale":null},"gt_translate_keys":[{"key":"link","format":"url"}],"_links":{"self":[{"href":"https:\/\/prohoster.info\/sk\/wp-json\/wp\/v2\/posts\/31905","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/prohoster.info\/sk\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/prohoster.info\/sk\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/prohoster.info\/sk\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/prohoster.info\/sk\/wp-json\/wp\/v2\/comments?post=31905"}],"version-history":[{"count":0,"href":"https:\/\/prohoster.info\/sk\/wp-json\/wp\/v2\/posts\/31905\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/prohoster.info\/sk\/wp-json\/wp\/v2\/media\/23765"}],"wp:attachment":[{"href":"https:\/\/prohoster.info\/sk\/wp-json\/wp\/v2\/media?parent=31905"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/prohoster.info\/sk\/wp-json\/wp\/v2\/categories?post=31905"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/prohoster.info\/sk\/wp-json\/wp\/v2\/tags?post=31905"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}