{"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\/sv\/blog\/administrirovanie\/happy-party-ili-para-strok-vospominanij-o-znakomstve-s-sektsionirovaniem-v-postgresql10","title":{"rendered":"Happy Party eller n\u00e5gra rader med minnen om att l\u00e4ra sig sektionering i PostgreSQL10.","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"

F\u00f6rord eller hur id\u00e9n om sektionering uppstod<\/h4>\n

\nB\u00f6rjan av historien h\u00e4r: Kommer du ih\u00e5g hur allt b\u00f6rjade? Allt var f\u00f6rsta g\u00e5ngen och p\u00e5 nytt.<\/a><\/noindex> Efter att n\u00e4stan alla resurser f\u00f6r optimering av f\u00f6rfr\u00e5gan vid den tidpunkten hade utt\u00f6mts, uppstod fr\u00e5gan - vad h\u00e4nder h\u00e4rn\u00e4st? S\u00e5 f\u00f6ddes id\u00e9n om sektionering. <\/p>\n

\"Happy
\n
\nEtt lyriskt avsnitt:<\/b>
\n\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 som det visade sig, fanns det outnyttjade reserver f\u00f6r optimering<\/a><\/noindex>. Tack asmm<\/a><\/noindex> och Habr !<\/i><\/p>\n

S\u00e5 hur kan man g\u00f6ra kunden lite lyckligare och samtidigt f\u00f6rb\u00e4ttra sina egna f\u00e4rdigheter? <\/p>\n

Om man f\u00f6renklar allt<\/b>, finns det i grunden tv\u00e5 s\u00e4tt att radikalt f\u00f6rb\u00e4ttra databasens prestanda:
\n1) Extensiv v\u00e4g - \u00f6ka resurser, \u00e4ndra konfiguration;
\n2) Intensiv v\u00e4g - optimera f\u00f6rfr\u00e5gningar<\/p>\n

Eftersom det, som jag upprepar, vid den tidpunkten redan var oklart vad som mer skulle \u00e4ndras i f\u00f6rfr\u00e5gan f\u00f6r att \u00f6ka hastigheten, valdes v\u00e4gen - \u00e4ndringar i tabellens design.<\/b><\/p>\n

S\u00e5 - den huvudsakliga fr\u00e5gan uppst\u00e5r - vad och hur ska vi f\u00f6r\u00e4ndra? <\/b>
\n<\/a><\/noindex><\/p>\n

Ursprungliga f\u00f6rh\u00e5llanden<\/h2>\n

\nF\u00f6r det f\u00f6rsta, h\u00e4r \u00e4r en s\u00e5dan ERD (visas f\u00f6renklat):
\n\"Happy
\nHuvudfunktioner:<\/p>\n

    \n
  1. relationer \u2018m\u00e5nga till m\u00e5nga\u2019<\/li>\n
  2. tabellen har redan en potentiell sektioneringsnyckel <\/li>\n<\/ol>\n

    Ursprunglig f\u00f6rfr\u00e5gan:<\/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
    \nResultat av k\u00f6rningen p\u00e5 testdatabasen:<\/b>
    \nKostnad <\/b>: 502 997.55
    \nK\u00f6rningstid<\/b>: 505 sekunder.<\/p>\n
    Vad ser vi? En vanlig f\u00f6rfr\u00e5gan, baserat p\u00e5 tidsintervallet. 
    \nVi g\u00f6r en enkel logisk slutsats: om det finns ett urval av en tidsram, hj\u00e4lper det oss? R\u00e4tt \u2014 partitionering.<\/p>\n
    Vad ska partitioneras?<\/h2>\n
    \nVid f\u00f6rsta anblick verkar valet uppenbart \u2014 deklarativ partitionering av tabellen \"shipment\" baserat p\u00e5 nyckeln \"SHIPMENT_DATE\" (f\u00f6r att g\u00e5 lite f\u00f6r l\u00e5ngt fram \u2014 i slut\u00e4ndan blev det inte riktigt s\u00e5 i produktion<\/i>). <\/p>\n
    Hur partitionerar man?<\/h2>\n
    \nDenna fr\u00e5ga \u00e4r inte heller s\u00e4rskilt sv\u00e5r. Tack och lov, i PostgreSQL 10 finns det nu ett m\u00e4nskligt v\u00e4nligt partitioneringssystem. 
    \nS\u00e5: <\/p>\n
      \n
    1.  Spara en dump av den ursprungliga tabellen \u2014 pg_dump source_table<\/i><\/li>\n
    2.  Ta bort den ursprungliga tabellen \u2014 drop table source_table<\/i><\/li>\n
    3. Skapa en f\u00f6r\u00e4ldratabell med partitionering efter intervall \u2014 create table source_table<\/i><\/li>\n
    4.  Skapa partitioner \u2014 create table source_table, create index<\/i><\/li>\n
    5.  Importera dumpen som skapades i steg 1 \u2014 pg_restore<\/i><\/li>\n<\/ol>\n
      <\/p>\n
      Skript f\u00f6r partitionering <\/h2>\n
      \nF\u00f6r enkelhetens skull har steg 2, 3, 4 sammanfogats i ett enda skript. <\/p>\n
      S\u00e5: 
      \nSpara en dump av den ursprungliga tabellen<\/b><\/p>\n
      pg_dump postgres --file=\\\/dump\\\/shipment.dmp --format=c --table=shipment --verbose > \\\/dump\\\/shipment.log 2>&1<\/code><\/pre>\n
      \nTa bort den ursprungliga tabellen + Skapa en f\u00f6r\u00e4ldratabell med partitionering efter intervall + Skapa partitioner<\/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 'SKAPA TILLF\u00c4LIG TABELL F\u00d6R LEVERANS_DATUM';\n  CREATE TEMP TABLE tmp_shipment_date as select distinct \"SHIPMENT_DATE\" from shipment order by \"SHIPMENT_DATE\" ;\n\n  RAISE NOTICE 'TA BORT TABELL LEVERANS';\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 'SKAPA PARTITIONER F\u00d6R TABELL LEVERANS';\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 'LEVERANS_DATUM=%',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       --NYA gr\u00e4nser endast f\u00f6r andra g\u00e5ngen och fram\u00e5t\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 'INDEXNAMN =%',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      --Ta bort f\u00f6rsta g\u00e5ngen flagga\n      first_flag := false ;\n   \n  END LOOP;\n\nend\n$$;<\/code><\/pre>\n
      \nImportera 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
      Kontrollera resultaten av partitioneringen<\/h2>\n
      \nVad har vi d\u00e5 i resultat? Den fullst\u00e4ndiga texten av planen \u00e4r stor och tr\u00e5kig, s\u00e5 det r\u00e4cker att begr\u00e4nsa sig till de slutliga siffrorna.<\/p>\n
      Det var<\/h3>\n
      \nKostnad:<\/b> 502 997.55
      \nUtf\u00f6rande tid:<\/b> 505 sekunder.<\/p>\n
      Det blev<\/h3>\n
      \nKostnad:<\/b> 77 872.36
      \nUtf\u00f6rande tid:<\/b> 79 sekunder.<\/p>\n
      Ett ganska bra resultat. Vi minskade kostnaden och utf\u00f6randetiden. S\u00e5ledes ger anv\u00e4ndningen av partitionering det f\u00f6rv\u00e4ntade resultatet och \u00f6ver lag \u2014 utan \u00f6verraskningar. <\/p>\n
      Gl\u00e4dja best\u00e4llaren<\/h2>\n
      \nTestresultaten presenterades f\u00f6r best\u00e4llaren f\u00f6r granskning. Efter genomg\u00e5ngen kom en n\u00e5got ov\u00e4ntad dom: \"Utm\u00e4rkt, partitionera tabellen 'data'.\"<\/p>\n
      Ja, men vi har ju studerat helt andra tabellen 'shipment', tabellen 'data' har inte f\u00e4ltet 'SHIPMENT_DATE'.<\/p>\n
      Ingen fara, l\u00e4gg till, \u00e4ndra. Det viktigaste \u00e4r att best\u00e4llaren \u00e4r n\u00f6jd med vad som kommer att bli resultatet, detaljerna i implementeringen \u00e4r inte s\u00e5 viktiga.<\/p>\n
      Vi partitionerar huvudtabellen 'data'<\/h2>\n
      \nP\u00e5 det hela ingen s\u00e4rskild sv\u00e5righet d\u00f6k upp. \u00c4ven om algoritmen f\u00f6r partitionering sj\u00e4lvklart har f\u00f6r\u00e4ndrats n\u00e5got.<\/p>\n
      Vi l\u00e4gger till kolumnen 'SHIPMENT_DATE' i tabellen 'data'<\/b><\/p>\n
      psql -h v\u00e4rd -U databas -d anv\u00e4ndare\n=> ALTER TABLE data ADD COLUMN \"SHIPMENT_DATE\" timestamp without time zone ;<\/code><\/pre>\n
      Vi fyller kolumnens v\u00e4rden 'SHIPMENT_DATE' i tabellen 'data' med v\u00e4rdena fr\u00e5n den namngivna kolumnen i tabellen 'shipment'<\/b><\/p>\n
      -----------------------------\n--update_data.sql\n--uppdaterar f\u00f6r den \u00e4ndrade tabellen \"data\" till v\u00e4rden av \"shipment_data\" fr\u00e5n tabellen \"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
      \nVi sparar dumpen av tabellen 'data'<\/b><\/p>\n
      pg_dump postgres --file=\\\/dump\\\/data.dmp --format=c --table=data --verbose > \\\/dump\\\/data.log 2>&1<\\\/source<\/code><\/pre>\n
      Vi \u00e5terskapar den partitionerade tabellen 'data'<\/b><\/p>\n
      --create_partition_data.sql\n--skapa partitioner f\u00f6r tabellen \"wafer data\" efter intervallet \"shipment_data\" med en m\u00e5nads varaktighet\n--version 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 'SKAPA TILLF\u00c4LLIG TABELL F\u00d6R 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 'RADERA TABELL data';\n  drop table data cascade ;\n\n\n  RAISE NOTICE 'SKAPA PARTITIONERAD TABELL 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 'SKAPA PARTITIONER F\u00d6R TABELL 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 gr\u00e4nser\n      IF   begin_year = '0' THEN\n       RAISE NOTICE '***Init gr\u00e4nser';\n       first_flag := true ; --first time 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 '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      -- Kontrollera aktuellt datum i gr\u00e4nser INTE f\u00f6r f\u00f6rsta g\u00e5ngen\n\n      RAISE NOTICE 'Aktuella data = %',to_char( to_date( current_year||'.'||current_month, 'YYYY.MM'), 'YYYY.MM');\n      RAISE NOTICE 'B\u00f6rja data = %',to_char( to_date( begin_year||'.'||begin_month, 'YYYY.MM'), 'YYYY.MM');\n      RAISE NOTICE 'N\u00e4sta data = %',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 '***Forts\u00e4tt';\n         CONTINUE ; \n      ELSE\n       --NYA gr\u00e4nser endast f\u00f6r andra och efterf\u00f6ljande g\u00e5nger \n       RAISE NOTICE '***NYA GR\u00c4NSER';\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 'PARTITIONNUMMER % , TABELLNAMN =%',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 'INDEXNAMN =%',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 'INDEXNAMN =%',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 'INDEXNAMN =%',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 'INDEXNAMN =%',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 'INDEXNAMN =%',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      --Ta bort f\u00f6rsta tidsflaggan\n      first_flag := false ;\n\n  END LOOP;\nend\n$$;\n<\/code><\/pre>\n
      \nLaddar upp dumpfilen som skapades i steg 3.<\/b><\/p>\n
      pg_restore -h v\u00e4rd -user -d databas --data-only --format=c --table=data --verbose data.dmp > data_restore.log 2>&1<\/code><\/pre>\n
      \nSkapar en separat sektion f\u00f6r gamla data<\/b><\/p>\n
      ---------------------------------------------------\n--create_partition_for_old_dates.sql\n--skapa partitioner f\u00f6r att beh\u00e5lla gamla datum\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 'Gammalt datum \u00e4r %',rec_shipment_date.min_date ;\n\n      partition_name := 'data_old_dates'  ;\n\n      RAISE NOTICE 'PARTITIONSNAMNET \u00c4R %',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
      Slutresultat:<\/h3>\n
      \nDet var<\/b>
      \nKostnad:<\/b> 502 997.55
      \nK\u00f6rningstid<\/b>: 505 sekunder.<\/p>\n
      Det blev<\/b>
      \nKostnad:<\/b> 68 533.70
      \nUtf\u00f6rande tid:<\/b> 69 sekunder<\/p>\n
      V\u00e4rdigt, helt v\u00e4rdigt. Och med tanke p\u00e5 att vi under v\u00e4gen lyckades l\u00e4ra oss mekanismen f\u00f6r partitionering i PostgreSQL 10 \u2013 Ett utm\u00e4rkt resultat.<\/p>\n
      En lyrisk avstickare<\/h2>\n
      \n\u0410 \u043c\u043e\u0436\u043d\u043e, \u0441\u0434\u0435\u043b\u0430\u0442\u044c \u0435\u0449\u0435 \u043b\u0443\u0447\u0448\u0435 — \u0414\u0410, \u041c\u041e\u0416\u041d\u041e!<\/b>F\u00f6r detta beh\u00f6ver vi anv\u00e4nda 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
      \nSkriver om fr\u00e5gan igen:
      \nFr\u00e5ga med anv\u00e4ndning av 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
      \nOch vi f\u00e5r ytterligare en slutsats:<\/b>
      \nDet var<\/b>
      \nKostnad:<\/b> 502 997.55
      \nK\u00f6rningstid<\/b>: 505 sekunder<\/p>\n
      Det blev<\/b>
      \nKostnad:<\/b> 42 481.16
      \nUtf\u00f6rande tid:<\/b> 43 sekunder.<\/p>\n
      \u00c4ven om, s\u00e5 klart, ett s\u00e5 lovande resultat kan vara bedr\u00e4gligt; presentationerna m\u00e5ste ju uppdateras. S\u00e5 det slutliga datainsamlingstiden kommer inte att hj\u00e4lpa s\u00e5 mycket. Men som experiment \u00e4r det ganska intressant.<\/p>\n
      I sj\u00e4lva verket, som det visade sig, tackar vi igen asmm<\/a><\/noindex> och Habr !- fr\u00e5gan kan f\u00f6rb\u00e4ttras ytterligare. <\/a><\/noindex><\/p>\n
      Epilog<\/h2>\n
      \nS\u00e5, kunden \u00e4r n\u00f6jd. Och beh\u00f6ver <\/b>utnyttjar situationen. <\/p>\n
      Ny uppgift<\/b>: Vad kan vi komma p\u00e5 f\u00f6r att f\u00f6rdjupa och utvidga?<\/p>\n
      Och h\u00e4r kommer jag att t\u00e4nka p\u00e5 - killar, vi har ingen \u00f6vervakning av v\u00e5ra PostgreSQL-databaser.<\/p>\n
      \u00c4rligt talat, det finns viss \u00f6vervakning genom Cloud Watch p\u00e5 AWS. Men vilken nytta har den \u00f6vervakningen f\u00f6r DBA? I stort sett ingen.<\/p>\n
      Om det finns en m\u00f6jlighet att g\u00f6ra n\u00e5got anv\u00e4ndbart och intressant f\u00f6r sig sj\u00e4lv, kan man inte missa en s\u00e5dan chans \u2026
      \nEFTER SOM
      \n<\/b>
      \n\"Happy
      \n
      \nS\u00e5 h\u00e4r kom vi till det mest intressanta:<\/p>\n
      3:e december 2018.<\/b>
      \nBeslutet att p\u00e5b\u00f6rja arbetet med att unders\u00f6ka de tillg\u00e4ngliga m\u00f6jligheterna f\u00f6r \u00f6vervakning av prestanda f\u00f6r PostgreSQL-fr\u00e5gor.\n<\/p><\/blockquote>\n
      Men det \u00e4r redan en helt annan historia.<\/b><\/p>\n
      \u041f\u0440\u043e\u0434\u043e\u043b\u0436\u0435\u043d\u0438\u0435, \u0441\u043b\u0435\u0434\u0443\u0435\u0442…<\/i>
      \n
      K\u00e4lla:       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 eller n\u00e5gra rader med minnen fr\u00e5n m\u00f6tet med partitionering i PostgreSQL10 | ProHoster","description":"F\u00f6rord eller hur id\u00e9n om partitionering uppstod. Historien b\u00f6rjar h\u00e4r: Kommer du ih\u00e5g hur allt b\u00f6rjade.","canonical_url":"https:\/\/prohoster.info\/sv\/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":"sv_SE","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\/sv\/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\/sv\/wp-json\/wp\/v2\/posts\/31905","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/prohoster.info\/sv\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/prohoster.info\/sv\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/prohoster.info\/sv\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/prohoster.info\/sv\/wp-json\/wp\/v2\/comments?post=31905"}],"version-history":[{"count":0,"href":"https:\/\/prohoster.info\/sv\/wp-json\/wp\/v2\/posts\/31905\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/prohoster.info\/sv\/wp-json\/wp\/v2\/media\/23765"}],"wp:attachment":[{"href":"https:\/\/prohoster.info\/sv\/wp-json\/wp\/v2\/media?parent=31905"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/prohoster.info\/sv\/wp-json\/wp\/v2\/categories?post=31905"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/prohoster.info\/sv\/wp-json\/wp\/v2\/tags?post=31905"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}