{"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\/sq\/blog\/administrirovanie\/happy-party-ili-para-strok-vospominanij-o-znakomstve-s-sektsionirovaniem-v-postgresql10","title":{"rendered":"Happy Party ose disa rreshta-kujtime mbi njohjen me seksionimin n\u00eb PostgreSQL10","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"

Parath\u00ebnie, ose si lindi ideja e particionimit<\/h4>\n

\nFillimi i historis\u00eb \u00ebsht\u00eb k\u00ebtu: A t\u00eb kujtohet si filloi gjith\u00e7ka. Gjith\u00e7ka ishte p\u00ebr her\u00eb t\u00eb par\u00eb dhe p\u00ebrs\u00ebri nga e para.<\/a><\/noindex> Pasi pothuajse t\u00eb gjitha burimet p\u00ebr optimizimin e k\u00ebrkes\u00ebs, n\u00eb at\u00eb moment, ishin shteruar, u ngrit pyetja \u2014 \u00e7far\u00eb b\u00ebjm\u00eb m\u00eb tej? K\u00ebshtu edhe lindi ideja e particionimit. <\/p>\n

\"Happy
\n
\nNj\u00eb digresion lirik:<\/b>
\nAjo pik\u00ebrisht n\u00eb at\u00eb moment, sepse si\u00e7 doli, kishte ende rezerva t\u00eb pashfryt\u00ebzuara p\u00ebr optimizim<\/a><\/noindex>. Faleminderit asmm<\/a><\/noindex> dhe Habr-it!<\/i><\/p>\n

Pra, si mund ta b\u00ebjm\u00eb klientin disi t\u00eb k\u00ebnaqur dhe nj\u00ebkoh\u00ebsisht t\u00eb p\u00ebrmir\u00ebsojm\u00eb aft\u00ebsit\u00eb tona? <\/p>\n

N\u00ebse e thjeshtojm\u00eb gjith\u00e7ka n\u00eb maksimum<\/b>, at\u00ebher\u00eb ka vet\u00ebm dy m\u00ebnyra p\u00ebr t\u00eb p\u00ebrmir\u00ebsuar rr\u00ebnj\u00ebsisht performanc\u00ebn e baz\u00ebs s\u00eb t\u00eb dh\u00ebnave:
\n1) Rruga ekstensiv\u0435 \u2014 shtojm\u00eb burimet, ndryshojm\u00eb konfigurimin;
\n2) Rruga intensive \u2014 optimizimi i k\u00ebrkesave<\/p>\n

Meq\u00eb, si\u00e7 e p\u00ebrs\u00ebris, n\u00eb at\u00eb moment nuk ishte m\u00eb e qart\u00eb se \u00e7far\u00eb tjet\u00ebr mund t\u00eb ndryshohej n\u00eb k\u00ebrkes\u00eb p\u00ebr ta p\u00ebrshpejtuar, u zgjodh rruga e ndryshimit t\u00eb dizajnit t\u00eb tabelave.<\/b><\/p>\n

Pra, lind pyetja kryesore \u2014 \u00e7far\u00eb dhe si do t\u00eb ndryshojm\u00eb? <\/b>
\n<\/a><\/noindex><\/p>\n

Kushtet fillestare<\/h2>\n

\nS\u00eb pari, kemi nj\u00eb ERD t\u00eb till\u00eb (t\u00eb paraqitur n\u00eb m\u00ebnyr\u00eb t\u00eb thjeshtuar me kusht):
\n\"Happy
\nKarakteristikat kryesore:<\/p>\n

    \n
  1. marr\u00ebdh\u00ebnie \u201cshum\u00eb me shum\u00eb\u201d<\/li>\n
  2. tabela tashm\u00eb ka nj\u00eb \u00e7el\u00ebs t\u00eb mundsh\u00ebm particionimi <\/li>\n<\/ol>\n

    K\u00ebrkesa fillestare:<\/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
    \nRezultatet e ekzekutimit n\u00eb baz\u00ebn e t\u00eb dh\u00ebnave testuese:<\/b>
    \nKosto <\/b>: 502 997.55
    \nKoha e ekzekutimit<\/b>: 505 sekonda.<\/p>\n
    \u00c7far\u00eb shohim? Nj\u00eb k\u00ebrkes\u00eb e zakonshme, sipas nj\u00eb intervali kohor. 
    \nB\u00ebjm\u00eb nj\u00eb supozim logjik shum\u00eb t\u00eb thjesht\u00eb: n\u00ebse kemi nj\u00eb most\u00ebr t\u00eb nj\u00eb prerjeje kohore, \u00e7far\u00eb do t\u00eb na ndihmoj\u00eb? Sakt\u00eb \u2014 particionimi.<\/p>\n
    \u00c7far\u00eb t\u00eb particionohet?<\/h2>\n
    \nN\u00eb pamje t\u00eb par\u00eb, zgjedhja \u00ebsht\u00eb e qart\u00eb \u2014 particionimi deklarativ i tabel\u00ebs \u00abshipment\u00bb sipas \u00e7el\u00ebsit \u00abSHIPMENT_DATE\u00bb (duke e paraprir\u00eb shum\u00eb ngjarjet \u2014 n\u00eb fund n\u00eb production doli pak ndryshe<\/i>). <\/p>\n
    Si t\u00eb particionohet?<\/h2>\n
    \nEdhe kjo pyetje nuk \u00ebsht\u00eb shum\u00eb e v\u00ebshtir\u00eb. P\u00ebr fat, n\u00eb PostgreSQL 10 tani ekziston nj\u00eb mekaniz\u00ebm njer\u00ebzor particionimi. 
    \nPra: <\/p>\n
      \n
    1.  Ruajm\u00eb dump-in e tabel\u00ebs burimore \u2014 pg_dump source_table<\/i><\/li>\n
    2.  Fshijm\u00eb tabel\u00ebn burimore \u2014 drop table source_table<\/i><\/li>\n
    3. Krijojm\u00eb tabel\u00ebn prind me particionim sipas intervalit \u2014 create table source_table<\/i><\/li>\n
    4.  Krijojm\u00eb particionet \u2014 create table source_table, create index<\/i><\/li>\n
    5.  Importojm\u00eb dump-in e krijuar n\u00eb hapin 1 \u2014 pg_restore<\/i><\/li>\n<\/ol>\n
      <\/p>\n
      Skriptet p\u00ebr particionim <\/h2>\n
      \nP\u00ebr thjesht\u00ebsi dhe leht\u00ebsi p\u00ebrdorimi, hapat 2, 3, 4 u bashkuan n\u00eb nj\u00eb skript t\u00eb vet\u00ebm. <\/p>\n
      Pra: 
      \nRuajm\u00eb dump-in e tabel\u00ebs burimore<\/b><\/p>\n
      pg_dump postgres --file=\/dump\/shipment.dmp --format=c --table=shipment --verbose > \/dump\/shipment.log 2>&1<\/code><\/pre>\n
      \nFshijm\u00eb tabel\u00ebn burimore + Krijojm\u00eb tabel\u00ebn prind me particionim sipas intervalit + Krijojm\u00eb particionet<\/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 'CREATE TEMPORARY TABLE FOR SHIPMENT_DATE';\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 'CREATE PARTITIONS FOR TABLE 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       --NEW borders only for second and after time \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 first time flag\n      first_flag := false ;\n   \n  END LOOP;\n\nend\n$$;<\/code><\/pre>\n
      \nImportojm\u00eb dump-in<\/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
      Kontrollojm\u00eb rezultatet e particionimit<\/h2>\n
      \n\u00c7far\u00eb kemi si p\u00ebrfundim? Teksti i plot\u00eb i planit t\u00eb ekzekutimit \u00ebsht\u00eb i gjat\u00eb dhe i m\u00ebrzitsh\u00ebm, prandaj mund t\u00eb kufizohemi te shifrat p\u00ebrfundimtare.<\/p>\n
      Ishte<\/h3>\n
      \nKostoja:<\/b> 502 997.55
      \nKoha e ekzekutimit:<\/b> 505 sekonda.<\/p>\n
      U b\u00eb<\/h3>\n
      \nKostoja:<\/b> 77 872.36
      \nKoha e ekzekutimit:<\/b> 79 sekonda.<\/p>\n
      Nj\u00eb rezultat mjaft i mir\u00eb. Ul\u00ebm koston dhe koh\u00ebn e ekzekutimit. K\u00ebshtu, p\u00ebrdorimi i particionimit jep efektin e pritur dhe, n\u00eb p\u00ebrgjith\u00ebsi, pa surpriza. <\/p>\n
      Ta g\u00ebzojm\u00eb klientin<\/h2>\n
      \nRezultatet e testimit iu paraqit\u00ebn klientit p\u00ebr shqyrtim. Dhe pas njohjes me to, u dha nj\u00eb verdikt disi i papritur: \u00abShk\u00eblqyesh\u00ebm, particiononi tabel\u00ebn \u00abdata\u00bb\u00bb.<\/p>\n
      Po, por ne po studionim nj\u00eb tabel\u00eb krejt tjet\u00ebr, \u00abshipment\u00bb; tabela \u00abdata\u00bb nuk ka fush\u00ebn \u00abSHIPMENT_DATE\u00bb.<\/p>\n
      Nuk \u00ebsht\u00eb problem, shtojeni, ndryshojeni. Kryesorja \u00ebsht\u00eb q\u00eb klienti t\u00eb jet\u00eb i k\u00ebnaqur me rezultatin p\u00ebrfundimtar; holl\u00ebsit\u00eb e zbatimit nuk jan\u00eb edhe aq t\u00eb r\u00ebnd\u00ebsishme.<\/p>\n
      Particionojm\u00eb tabel\u00ebn kryesore \u00abdata\u00bb<\/h2>\n
      \nN\u00eb p\u00ebrgjith\u00ebsi, nuk pati ndonj\u00eb v\u00ebshtir\u00ebsi t\u00eb ve\u00e7ant\u00eb. Megjithat\u00eb, algoritmi i particionimit, natyrisht, ndryshoi disi.<\/p>\n
      Shtojm\u00eb kolon\u00ebn \u00abSHIPMENT_DATA\u00bb n\u00eb tabel\u00ebn \u00abdata\u00bb<\/b><\/p>\n
      psql -h host -U baz\u00eb -d p\u00ebrdorues\n=> ALTER TABLE data ADD COLUMN \"SHIPMENT_DATE\" timestamp without time zone ;<\/code><\/pre>\n
      Plot\u00ebsojm\u00eb vlerat e kolon\u00ebs \u00abSHIPMENT_DATA\u00bb n\u00eb tabel\u00ebn \u00abdata\u00bb me vlerat e kolon\u00ebs me t\u00eb nj\u00ebjtin em\u00ebr nga tabela \u00abshipment\u00bb<\/b><\/p>\n
      -----------------------------\n--update_data.sql\n--updating for altered table \"data\" to values of \"shipment_data\" from the table \"shipment\"\n--version 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
      \nRuajm\u00eb dump-in e tabel\u00ebs \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
      Rikrijojm\u00eb tabel\u00ebn e particionuar \u00abdata\u00bb<\/b><\/p>\n
      --create_partition_data.sql\n--krijo particione p\u00ebr tabel\u00ebn \"wafer data\" sipas kolon\u00ebs s\u00eb intervalit \"shipment_data\" me koh\u00ebzgjatje nj\u00eb mujore\n--versioni 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 'KRIJO TABEL\u00cb T\u00cb P\u00cbRKOHSHME P\u00cbR 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 'FSHI TABEL\u00cbN data';\n  drop table data cascade ;\n\n\n  RAISE NOTICE 'KRIJO TABEL\u00cbN E PARTICIONUAR 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 'KRIJO PARTICIONE P\u00cbR TABEL\u00cbN 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      --Inicializo kufijt\u00eb\n      IF   begin_year = '0' THEN\n       RAISE NOTICE '***Inicializo kufijt\u00eb';\n       first_flag := true ; --flamur p\u00ebr her\u00ebn e par\u00eb\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      -- Kontrollo dat\u00ebn aktuale brenda kufijve, JO p\u00ebr her\u00ebn e par\u00eb\n\n      RAISE NOTICE 'T\u00eb dh\u00ebnat aktuale = %',to_char( to_date( current_year||'.'||current_month, 'YYYY.MM'), 'YYYY.MM');\n      RAISE NOTICE 'T\u00eb dh\u00ebnat e fillimit = %',to_char( to_date( begin_year||'.'||begin_month, 'YYYY.MM'), 'YYYY.MM');\n      RAISE NOTICE 'T\u00eb dh\u00ebnat pasuese = %',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 '***VAZHDO';\n         CONTINUE ; \n      ELSE\n       --Kufij t\u00eb RINJ vet\u00ebm nga hera e dyt\u00eb e tutje \n       RAISE NOTICE '***KUFIJ T\u00cb RINJ';\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 'NUMRI I PARTICIONIT % , EMRI I TABEL\u00cbS =%',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 'EMRI I INDEKSIT =%',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 'EMRI I INDEKSIT =%',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 'EMRI I INDEKSIT =%',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 'EMRI I INDEKSIT =%',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 'EMRI I INDEKSIT =%',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      --Hiq flamurin e her\u00ebs s\u00eb par\u00eb\n      first_flag := false ;\n\n  END LOOP;\nend\n$$;\n<\/code><\/pre>\n
      \nNgarkojm\u00eb dump-in e krijuar n\u00eb hapin 3.<\/b><\/p>\n
      pg_restore -h \u0445\u043e\u0441\u0442 -\u044e\u0437\u0435\u0440 -d \u0431\u0430\u0437\u0430 --data-only --format=c --table=data --verbose  data.dmp > data_restore.log 2>&1<\/code><\/pre>\n
      \nKrijojm\u00eb nj\u00eb seksion t\u00eb ve\u00e7ant\u00eb p\u00ebr t\u00eb dh\u00ebnat e vjetra<\/b><\/p>\n
      ---------------------------------------------------\n--create_partition_for_old_dates.sql\n--create partitions for keeping old dates \n--version 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 'Old date is %',rec_shipment_date.min_date ;\n\n      partition_name := 'data_old_dates'  ;\n\n      RAISE NOTICE 'PARTITION NAME IS %',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
      Rezultatet p\u00ebrfundimtare:<\/h3>\n
      \nIshte<\/b>
      \nKostoja:<\/b> 502 997.55
      \nKoha e ekzekutimit<\/b>: 505 sekonda.<\/p>\n
      U b\u00eb<\/b>
      \nKostoja:<\/b> 68 533.70
      \nKoha e ekzekutimit:<\/b> 69 sekonda<\/p>\n
      Shum\u00eb mir\u00eb, v\u00ebrtet shum\u00eb mir\u00eb. Sidomos duke pasur parasysh se gjat\u00eb procesit arrit\u00ebm t\u00eb kuptojm\u00eb pak a shum\u00eb edhe mekanizmin e particionimit n\u00eb PostgreSQL 10 \u2014 rezultat i shk\u00eblqyer.<\/p>\n
      Nj\u00eb hapje lirik\u00eb<\/h2>\n
      \nPo, mund t\u00eb b\u00ebjm\u00eb edhe m\u00eb mir\u00eb \u2014 PO, MUND!<\/b>P\u00ebr k\u00ebt\u00eb duhet t\u00eb p\u00ebrdoret 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
      \nE rishkruajm\u00eb edhe nj\u00eb her\u00eb k\u00ebrkes\u00ebn:
      \nK\u00ebrkes\u00eb duke p\u00ebrdorur 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
      \nDhe marrim edhe nj\u00eb rezultat p\u00ebrfundimtar:<\/b>
      \nIshte<\/b>
      \nKostoja:<\/b> 502 997.55
      \nKoha e ekzekutimit<\/b>: 505 sekonda<\/p>\n
      U b\u00eb<\/b>
      \nKostoja:<\/b> 42 481.16
      \nKoha e ekzekutimit:<\/b> 43 sekonda.<\/p>\n
      Megjith\u00ebse, sigurisht, ky rezultat kaq premtues \u00ebsht\u00eb mashtrues, sepse pamjet duhen rifreskuar. K\u00ebshtu q\u00eb koha p\u00ebrfundimtare e marrjes s\u00eb t\u00eb dh\u00ebnave nuk do t\u00eb ndihmoj\u00eb edhe aq shum\u00eb. Por si eksperiment, \u00ebsht\u00eb mjaft interesante.<\/p>\n
      N\u00eb fakt, si\u00e7 doli, edhe nj\u00eb her\u00eb faleminderit asmm<\/a><\/noindex> dhe Habr !- k\u00ebrkesa mund t\u00eb p\u00ebrmir\u00ebsohet edhe m\u00eb tej. <\/a><\/noindex><\/p>\n
      Pasth\u00ebnie<\/h2>\n
      \nPra, klienti \u00ebsht\u00eb i k\u00ebnaqur. Dhe t\u00eb shtoni nj\u00eb kolon\u00eb t\u00eb re - asnj\u00eb problem, m\u00eb posht\u00eb \u00ebsht\u00eb nj\u00eb zgjidhje e thjesht\u00eb nj\u00eb-linj\u00ebshe. Zgjidhja \u00ebsht\u00eb evolucioni i skem\u00ebs! <\/b>t\u00eb p\u00ebrfitojm\u00eb nga situata. <\/p>\n
      Detyr\u00eb e re<\/b>: \u00c7far\u00eb mund t\u00eb shpikim q\u00eb ta thellojm\u00eb dhe zgjerojm\u00eb?<\/p>\n
      Dhe k\u00ebtu kujtojm\u00eb \u2014 djema, ne n\u00eb fakt nuk kemi monitorim t\u00eb bazave tona t\u00eb t\u00eb dh\u00ebnave PostgreSQL.<\/p>\n
      T\u00eb themi t\u00eb drejt\u00ebn, nj\u00eb lloj monitorimi n\u00eb form\u00ebn e Cloud Watch n\u00eb AWS gjithsesi ekziston. Por \u00e7far\u00eb dobie ka ky monitorim p\u00ebr DBA? N\u00eb thelb, pothuajse asnj\u00eb.<\/p>\n
      N\u00ebse t\u00eb \u00ebsht\u00eb dh\u00ebn\u00eb mund\u00ebsia t\u00eb b\u00ebsh di\u00e7ka t\u00eb dobishme dhe interesante edhe p\u00ebr veten, nuk mund t\u00eb mos e shfryt\u00ebzosh nj\u00eb mund\u00ebsi t\u00eb till\u00eb \u2026
      \nSEPSE
      \n<\/b>
      \n\"Happy
      \n
      \nK\u00ebshtu iu afruam pjes\u00ebs m\u00eb interesante:<\/p>\n
      3 Dhjetor 2018.<\/b>
      \nMarrja e vendimit p\u00ebr t\u00eb nisur pun\u00ebn p\u00ebr studimin e mund\u00ebsive ekzistuese t\u00eb monitorimit t\u00eb performanc\u00ebs s\u00eb k\u00ebrkesave PostgreSQL.\n<\/p><\/blockquote>\n
      Por kjo \u00ebsht\u00eb tashm\u00eb nj\u00eb histori krejt tjet\u00ebr.<\/b><\/p>\n
      Vazhdimi, n\u00eb vijim\u2026<\/i>
      \n
      Burimi:       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 ose disa rreshta kujtimesh p\u00ebr njohjen me particionimin n\u00eb PostgreSQL10 | ProHoster","description":"Parath\u00ebnie, ose si lindi ideja e particionimit. Fillimi i historis\u00eb k\u00ebtu: A t\u00eb kujtohet si filloi gjith\u00e7ka.","canonical_url":"https:\/\/prohoster.info\/sq\/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":"sq_AL","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\/sq\/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\/sq\/wp-json\/wp\/v2\/posts\/31905","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/comments?post=31905"}],"version-history":[{"count":0,"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/posts\/31905\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/media\/23765"}],"wp:attachment":[{"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/media?parent=31905"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/categories?post=31905"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/tags?post=31905"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}