{"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\/ro\/blog\/administrirovanie\/happy-party-ili-para-strok-vospominanij-o-znakomstve-s-sektsionirovaniem-v-postgresql10","title":{"rendered":"Happy Party sau c\u00e2teva r\u00e2nduri de amintiri despre familiarizarea cu sec\u021bionarea \u00een PostgreSQL10","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"

Prefa\u021b\u0103 sau cum a ap\u0103rut ideea sec\u021bion\u0103rii<\/h4>\n

\nPovestea \u00eencepe aici: \u00ce\u021bi aminte\u0219ti cum a \u00eenceput totul. Totul era pentru prima oar\u0103 \u0219i din nou.<\/a><\/noindex> Dup\u0103 ce aproape toate resursele pentru optimizarea interog\u0103rii, la acel moment, au fost epuizate, s-a pus \u00eentrebarea - \u0219i ce urmeaz\u0103? A\u0219a a ap\u0103rut ideea sec\u021bion\u0103rii. <\/p>\n

\"Happy
\n
\nO digresiune liric\u0103:<\/b>
\nExact 'at that moment', because a\u0219a cum s-a dovedit, existau rezerve nefolosite de optimizare<\/a><\/noindex>. Mul\u021bumesc asmm<\/a><\/noindex> \u0219i Habr!<\/i><\/p>\n

A\u0219adar, cum putem face clientul oarecum fericit, \u00een acela\u0219i timp \u00eembun\u0103t\u0103\u021bindu-ne propriile abilit\u0103\u021bi? <\/p>\n

Dac\u0103 simplific\u0103m totul la maxim<\/b>, atunci, c\u0103ile de a \u00eembun\u0103t\u0103\u021bi radical performan\u021ba bazei de date sunt doar dou\u0103:
\n1) Calea extensiv\u0103 - cre\u0219tem resursele, schimb\u0103m configura\u021bia;
\n2) Calea intensiv\u0103 - optimizarea interog\u0103rilor<\/p>\n

\u00centruc\u00e2t, repet, la acel moment nu era clar ce s\u0103 mai schimb \u00een interogare pentru a accelera procesul, s-a ales calea - schimbarea designului tabelelor.<\/b><\/p>\n

A\u0219adar - apare \u00eentrebarea principal\u0103 - ce \u0219i cum vom schimba? <\/b>
\n<\/a><\/noindex><\/p>\n

Condi\u021biile ini\u021biale<\/h2>\n

\n\u00cen primul r\u00e2nd, avem un ERD astfel (prezentat schematic \u0219i simplificat):
\n\"Happy
\nCaracteristici principale:<\/p>\n

    \n
  1. rela\u021biile 'multe la multe'<\/li>\n
  2. tabelul are deja o poten\u021bial\u0103 cheie de sec\u021bionare <\/li>\n<\/ol>\n

    Interogarea ini\u021bial\u0103:<\/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
    \nRezultatele execu\u021biei pe baza de date de test:<\/b>
    \nCost <\/b>: 502 997.55
    \nTimp de execu\u021bie<\/b>: 505 secunde.<\/p>\n
    Ce vedem? O interogare obi\u0219nuit\u0103, pe un interval temporal. 
    \nFacem o presupunere logic\u0103 simpl\u0103: dac\u0103 exist\u0103 un e\u0219antion dintr-o fereastr\u0103 temporal\u0103, ne va ajuta? Corect \u2014 sec\u021bionarea.<\/p>\n
    Ce s\u0103 sec\u021bion\u0103m?<\/h2>\n
    \nLa prima vedere, alegerea este evident\u0103 \u2014 sec\u021bionarea declarativ\u0103 a tabelului \u201eshipment\u201d dup\u0103 cheia \u201eSHIPMENT_DATE\u201d (avans\u00e2nd pu\u021bin, \u00een produc\u021bie a ie\u0219it pu\u021bin diferit<\/i>). <\/p>\n
    Cum s\u0103 sec\u021bion\u0103m?<\/h2>\n
    \nAceast\u0103 \u00eentrebare nu este nici prea complicat\u0103. Din fericire, \u00een PostgreSQL 10, acum avem un mecanism de sec\u021bionare uman. 
    \nDeci: <\/p>\n
      \n
    1.  Salv\u0103m dump-ul tabelului surs\u0103 \u2014 pg_dump source_table<\/i><\/li>\n
    2.  \u0218tergem tabelul surs\u0103 \u2014 drop table source_table<\/i><\/li>\n
    3. Cre\u0103m tabelul p\u0103rinte cu sec\u021bionare pe baz\u0103 de interval \u2014 create table source_table<\/i><\/li>\n
    4.  Cre\u0103m sec\u021biuni \u2014 create table source_table, create index<\/i><\/li>\n
    5.  Import\u0103m dump-ul creat la pasul 1 \u2014 pg_restore<\/i><\/li>\n<\/ol>\n
      <\/p>\n
      Scripturi pentru sec\u021bionare <\/h2>\n
      \nPentru simplificare \u0219i confort, pa\u0219ii 2, 3, 4 au fost combina\u021bi \u00eentr-un singur script. <\/p>\n
      Deci: 
      \nSalv\u0103m dump-ul tabelului surs\u0103<\/b><\/p>\n
      pg_dump postgres --file=\\\/dump\\\/shipment.dmp --format=c --table=shipment --verbose > \\\/dump\\\/shipment.log 2>&1<\/code><\/pre>\n
      \n\u0218tergem tabelul surs\u0103 + Cre\u0103m tabelul p\u0103rinte cu sec\u021bionare pe baz\u0103 de interval + Cre\u0103m sec\u021biuni<\/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 'CREARE TABELA TEMPORAR\u0102 PENTRU DATA LIVR\u0102RII';\n  CREATE TEMP TABLE tmp_shipment_date as select distinct \"SHIPMENT_DATE\" from shipment order by \"SHIPMENT_DATE\" ;\n\n  RAISE NOTICE 'DROP TABLE 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 'CREARE PARTICI pentru tabela 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       --NOI limite doar pentru a doua \u0219i dup\u0103 aceea\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 'INDEX NAME =%',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      --Drop prima dat\u0103 flag\n      first_flag := false ;\n   \n  END LOOP;\n\nend\n$$;<\/code><\/pre>\n
      \nImport\u0103m dump-ul<\/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
      Verific\u0103m rezultatele sec\u021bion\u0103rii<\/h2>\n
      \nCe avem ca rezultat? Textul complet al planului de execu\u021bie este lung \u0219i plictisitor, a\u0219a c\u0103 s-ar putea s\u0103 ne limit\u0103m la cifrele centrale.<\/p>\n
      A fost<\/h3>\n
      \nCost:<\/b> 502 997.55
      \nTimp de execu\u021bie:<\/b> 505 secunde.<\/p>\n
      A devenit<\/h3>\n
      \nCost:<\/b> 77 872.36
      \nTimp de execu\u021bie:<\/b> 79 secunde.<\/p>\n
      Rezultat destul de bun. Am redus costul \u0219i timpul de execu\u021bie. Astfel, utilizarea sec\u021bion\u0103rii ofer\u0103 efectul scontat \u0219i, \u00een general, f\u0103r\u0103 surprize. <\/p>\n
      Aproape de satisfac\u021bia clientului<\/h2>\n
      \nRezultatele test\u0103rii au fost prezentate clientului spre examinare. Iar dup\u0103 ce s-au familiarizat cu ele, au emis un verdict oarecum nea\u0219teptat: \u201eExcelent, sec\u021biona\u021bi tabelul \u00abdata\u00bb\u201d.<\/p>\n
      Da, dar am studiat un alt tabel \u00abshipment\u00bb, tabelul \u00abdata\u00bb nu are c\u00e2mpul \u00abSHIPMENT_DATE\u00bb.<\/p>\n
      Nicio problem\u0103, ad\u0103uga\u021bi, schimba\u021bi. Principalul este ca clientul s\u0103 fie mul\u021bumit de rezultatul final, detaliile implement\u0103rii nu sunt chiar at\u00e2t de importante.<\/p>\n
      Sec\u021bion\u0103m tabelul principal \u00abdata\u00bb<\/h2>\n
      \n\u00cen general, nu au ap\u0103rut dificult\u0103\u021bi deosebite. De\u0219i, algoritmul de sec\u021bionare, bine\u00een\u021beles, s-a schimbat pu\u021bin.<\/p>\n
      Ad\u0103ug\u0103m coloana \u00abSHIPMENT_DATE\u00bb \u00een tabelul \u00abdata\u00bb<\/b><\/p>\n
      psql -h gazd\u0103 -U baz\u0103 -d utilizator\n=> ALTER TABLE data ADD COLUMN \"SHIPMENT_DATE\" timestamp without time zone ;<\/code><\/pre>\n
      Popul\u0103m valorile coloanei \u00abSHIPMENT_DATE\u00bb \u00een tabelul \u00abdata\u00bb, cu valorile coloanei cu acela\u0219i nume din tabelul \u00abshipment\u00bb<\/b><\/p>\n
      -----------------------------\n--update_data.sql\n--actualizare pentru tabelul modificat \"data\" cu valorile din \"shipment_data\" din tabelul \"shipment\"\n--versiune 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 'Total %',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 'row count = % , from %',row_count,total_rows;\n  END LOOP;\n\nend\n$$;<\/code><\/pre>\n
      \nSalv\u0103m dump-ul tabelului \u00abdata\u00bb<\/b><\/p>\n
      pg_dump postgres --file=\\\/dump\\\/data.dmp --format=c --table=data --verbose > \\\/dump\\\/data.log 2>&1<\\\/source<\/code><\/pre>\n
      Recreem tabelul sec\u021bionat \u00abdata\u00bb<\/b><\/p>\n
      --create_partition_data.sql\n--crea\u021bi parti\u021bii pentru tabela \"wafer data\" pe baza coloanei \"shipment_data\" cu o durat\u0103 de o lun\u0103\n--versiunea 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 'CREA\u021aI TABEL TEMPORAR PENTRU SHIPMENT_DATE';\n  CREATE TEMP TABLE tmp_shipment_date as select distinct \"SHIPMENT_DATE\" from shipment order by \"SHIPMENT_DATE\" ;\n\n\n  RAISE NOTICE '\u0218TERGE\u021aI TABELA data';\n  drop table data cascade ;\n\n\n  RAISE NOTICE 'CREA\u021aI TABELA PARTI\u021aIONAT\u0102 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\n  RAISE NOTICE 'CREA\u021aI PARTI\u021aII PENTRU TABELA 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      --Init borders\n      IF   begin_year = '0' THEN\n       RAISE NOTICE '***Init borders';\n       first_flag := true ; --flag pentru prima dat\u0103\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 '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      -- Verifica\u021bi data curent\u0103 \u00een limite, NU pentru prima dat\u0103\n\n      RAISE NOTICE 'Data curent\u0103 = %',to_char( to_date( current_year||'.'||current_month, 'YYYY.MM'), 'YYYY.MM');\n      RAISE NOTICE 'Data de \u00eenceput = %',to_char( to_date( begin_year||'.'||begin_month, 'YYYY.MM'), 'YYYY.MM');\n      RAISE NOTICE 'Data urm\u0103toare = %',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 '***CONTINUA\u021aI';\n         CONTINUE ; \n      ELSE\n       --NOI limite doar pentru a doua \u0219i dup\u0103 aceea \n       RAISE NOTICE '***NOI LIMITE';\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\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 'NUM\u0102R PARTI\u021aIE % , NUME TABEL =%',i , partition_name;\n      \n      EXECUTE format('CREATE TABLE ' || 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 'NUME INDEX =%',index_name;\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      RAISE NOTICE 'NUME INDEX =%',index_name;\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      RAISE NOTICE 'NUME INDEX =%',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      index_name := partition_name||'_parameter_id_idx';\n      RAISE NOTICE 'NUME INDEX =%',index_name;\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      RAISE NOTICE 'NUME INDEX =%',index_name;\n      EXECUTE format('CREATE INDEX ' || quote_ident(index_name) || ' ON '|| quote_ident(partition_name) ||' USING btree ("SHIPMENT_DATE") TABLESPACE pg_default ' ) ; \n\n      --\u0218terge\u021bi flag-ul primei vizite\n      first_flag := false ;\n\n  END LOOP;\nend\n$$;\n<\/code><\/pre>\n
      \n\u00cenc\u0103rc\u0103m dump-ul creat la pasul 3.<\/b><\/p>\n
      pg_restore -h host -uuser -d baza --data-only --format=c --table=data --verbose data.dmp > data_restore.log 2>&1<\/code><\/pre>\n
      \nCre\u0103m o sec\u021biune separat\u0103 pentru datele vechi.<\/b><\/p>\n
      ---------------------------------------------------\n--create_partition_for_old_dates.sql\n--crea\u021bi parti\u021bii pentru p\u0103strarea datelor vechi \n--versiunea 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 'Data veche este %',rec_shipment_date.min_date ;\n\n      partition_name := 'data_old_dates'  ;\n\n      RAISE NOTICE 'NUMELE PARTI\u021aIEI ESTE %',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
      Rezultatele finale:<\/h3>\n
      \nA fost<\/b>
      \nCost:<\/b> 502 997.55
      \nTimp de execu\u021bie<\/b>: 505 secunde.<\/p>\n
      A devenit<\/b>
      \nCost:<\/b> 68 533.70
      \nTimp de execu\u021bie:<\/b> 69 secunde<\/p>\n
      Onorabil, destul de onorabil. \u0218i av\u00e2nd \u00een vedere c\u0103 pe parcurs am reu\u0219it s\u0103 \u00eenv\u0103\u021b mai mult sau mai pu\u021bin mecanismul de parti\u021bionare \u00een PostgreSQL 10 \u2014 Un rezultat excelent.<\/p>\n
      O mic\u0103 digresiune<\/h2>\n
      \nCan we make it even better \u2014 YES, WE CAN!<\/b>Pentru asta trebuie s\u0103 folosim 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
      \n\u00cenc\u0103 o dat\u0103 rescriem interogarea:
      \nInterogare folosind materialized view<\/b><\/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.\"STC_NAME\" AS STC_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 LASERMARK_VIEW 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
      \n\u0218i ob\u021binem \u00eenc\u0103 un rezultat:<\/b>
      \nA fost<\/b>
      \nCost:<\/b> 502 997.55
      \nTimp de execu\u021bie<\/b>: 505 secunde<\/p>\n
      A devenit<\/b>
      \nCost:<\/b> 42 481.16
      \nTimp de execu\u021bie:<\/b> 43 secunde.<\/p>\n
      De\u0219i, desigur, un rezultat at\u00e2t de promi\u021b\u0103tor este \u00een\u0219el\u0103tor; trebuie s\u0103 facem refresh pe reprezent\u0103ri. A\u0219a c\u0103 timpul final pentru ob\u021binerea datelor nu va ajuta prea mult. Dar ca experiment, este destul de interesant.<\/p>\n
      De fapt, dup\u0103 cum s-a dovedit, \u00eenc\u0103 o dat\u0103 mul\u021bumim asmm<\/a><\/noindex> \u0219i Habr !- interogarea poate fi \u00eembun\u0103t\u0103\u021bit\u0103 \u0219i mai mult. <\/a><\/noindex><\/p>\n
      Cuv\u00e2nt \u00eenainte<\/h2>\n
      \nDeci, clientul este mul\u021bumit. \u0218i nevoie <\/b>profit\u0103 de situa\u021bie. <\/p>\n
      Sarcin\u0103 nou\u0103<\/b>: Ce putem inventa pentru a aprofunda \u0219i extinde?<\/p>\n
      \u0218i aici \u00eemi amintesc \u2014 b\u0103ie\u021bi, dar noi nu avem monitorizare pentru bazele noastre de date PostgreSQL.<\/p>\n
      Pun\u00e2nd m\u00e2na pe inim\u0103, exist\u0103 un fel de monitorizare sub form\u0103 de Cloud Watch pe AWS. Dar ce folos are aceast\u0103 monitorizare pentru DBA? Practic, deloc.<\/p>\n
      Dac\u0103 a ap\u0103rut ocazia de a face ceva util \u0219i interesant \u0219i pentru mine, nu pot s\u0103 nu profit de o astfel de ocazie...
      \nC\u0102CI
      \n<\/b>
      \n\"Happy
      \n
      \nA\u0219a am ajuns la cel mai interesant subiect:<\/p>\n
      3 Decembrie 2018.<\/b>
      \nDecizia de a \u00eencepe lucr\u0103rile pentru a explora oportunit\u0103\u021bile de monitorizare a performan\u021bei interog\u0103rilor PostgreSQL.\n<\/p><\/blockquote>\n
      Dar aceasta este deja o poveste complet diferit\u0103.<\/b><\/p>\n
      To be continued\u2026<\/i>
      \n
      Sursa:       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\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 sau c\u00e2teva r\u00e2nduri de amintiri despre \u00eent\u00e2lnirea cu sec\u021bionarea \u00een PostgreSQL10 | ProHoster","description":"Prefa\u021b\u0103 sau cum a ap\u0103rut ideea sec\u021bion\u0103rii \u00cenceputul pove\u0219tii aici: \u00ce\u021bi aminte\u0219ti cum a \u00eenceput totul.","canonical_url":"https:\/\/prohoster.info\/ro\/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":"ro_RO","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\/ro\/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\/ro\/wp-json\/wp\/v2\/posts\/31905","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/prohoster.info\/ro\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/prohoster.info\/ro\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/prohoster.info\/ro\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/prohoster.info\/ro\/wp-json\/wp\/v2\/comments?post=31905"}],"version-history":[{"count":0,"href":"https:\/\/prohoster.info\/ro\/wp-json\/wp\/v2\/posts\/31905\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/prohoster.info\/ro\/wp-json\/wp\/v2\/media\/23765"}],"wp:attachment":[{"href":"https:\/\/prohoster.info\/ro\/wp-json\/wp\/v2\/media?parent=31905"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/prohoster.info\/ro\/wp-json\/wp\/v2\/categories?post=31905"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/prohoster.info\/ro\/wp-json\/wp\/v2\/tags?post=31905"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}