ProHoster > Blog > Ma'muriyat > Happy Party yoki PostgreSQL10-da bo'linish bilan tanishish haqida bir necha qator xotiralar

Happy Party yoki PostgreSQL10-da bo'linish bilan tanishish haqida bir necha qator xotiralar

Muqaddima yoki bo'lim g'oyasi qanday paydo bo'lgan

Hikoya shu yerda boshlanadi: Hammasi qanday boshlanganini eslaysizmi? Hamma narsa birinchi marta va yana bo'ldi. So'rovni optimallashtirish uchun deyarli barcha resurslar tugagandan so'ng, o'sha paytda savol tug'ildi - keyin nima qilish kerak? Shunday qilib, bo'linish g'oyasi paydo bo'ldi.

Happy Party yoki PostgreSQL10-da bo'linish bilan tanishish haqida bir necha qator xotiralar

Lirik chekinish:
Aynan "o'sha paytda", chunki ma'lum bo'lishicha, optimallashtirish uchun foydalanilmagan zaxiralar mavjud edi. Rahmat asmm va Habru!

Xo'sh, yana qanday qilib mijozni xursand qilish va shu bilan birga o'z mahoratingizni oshirish mumkin?

Hamma narsani iloji boricha soddalashtirish uchun, keyin ma'lumotlar bazasining ishlashini tubdan yaxshilashning faqat ikkita usuli mavjud:
1) Keng yo'l - biz resurslarni ko'paytiramiz, konfiguratsiyani o'zgartiramiz;
2) Intensiv yo'l - so'rovlarni optimallashtirish

Takror aytaman, o'sha paytda tezlashtirish so'rovida yana nimani o'zgartirish kerakligi aniq emas edi, yo'l tanlangan edi - stol dizaynidagi o'zgarishlar.

Shunday qilib, asosiy savol tug'iladi: biz nimani va qanday o'zgartiramiz?

Dastlabki shartlar

Birinchidan, bu ERD mavjud (shartli soddalashtirilgan tarzda ko'rsatilgan):
Happy Party yoki PostgreSQL10-da bo'linish bilan tanishish haqida bir necha qator xotiralar
Asosiy xususiyatlari:

  1. ko'p-ko'p munosabatlar
  2. jadvalda potentsial bo'lim kaliti allaqachon mavjud

Asl so'rov:

SELECT
            p."PARAMETER_ID" as  parameter_id,
            pc."PC_NAME" AS pc_name,
            pc."CUSTOMER_PARTNUMBER" AS customer_partnumber,
            w."LASERMARK" AS lasermark,
            w."LOTID" AS lotid,
            w."REPORTED_VALUE" AS reported_value,
            w."LOWER_SPEC_LIMIT" AS lower_spec_limit,
            w."UPPER_SPEC_LIMIT" AS upper_spec_limit,
            p."TYPE_CALCUL" AS type_calcul,
            s."SHIPMENT_NAME" AS shipment_name,
            s."SHIPMENT_DATE" AS shipment_date,
            extract(year from s."SHIPMENT_DATE") AS year,
            extract(month from s."SHIPMENT_DATE") as month,
            s."REPORT_NAME" AS report_name,
            p."SPARAM_NAME" AS SPARAM_name,
            p."CUSTOMERPARAM_NAME" AS customerparam_name
        FROM data w INNER JOIN shipment s ON s."SHIPMENT_ID" = w."SHIPMENT_ID"
             INNER JOIN parameters p ON p."PARAMETER_ID" = w."PARAMETER_ID"
             INNER JOIN shipment_pc sp ON s."SHIPMENT_ID" = sp."SHIPMENT_ID"
             INNER JOIN pc pc ON pc."PC_ID" = sp."PC_ID"
             INNER JOIN ( SELECT w2."LASERMARK" , MAX(s2."SHIPMENT_DATE") AS "SHIPMENT_DATE"
                          FROM shipment s2 INNER JOIN data w2 ON s2."SHIPMENT_ID" = w2."SHIPMENT_ID" 
                          GROUP BY w2."LASERMARK"
                         ) md ON md."SHIPMENT_DATE" = s."SHIPMENT_DATE" AND md."LASERMARK" = w."LASERMARK"
        WHERE 
             s."SHIPMENT_DATE" >= '2018-07-01' AND s."SHIPMENT_DATE" <= '2018-09-30' ;

Test ma'lumotlar bazasida bajarish natijalari:
XARAJATLAR : 502 997.55
Amalga oshirish vaqti: 505 soniya.

Biz nimani ko'ramiz? Vaqt bo'limiga asoslangan muntazam so'rov.
Keling, eng oddiy mantiqiy taxmin qilaylik: agar vaqt bo'limining namunasi bo'lsa, u bizga yordam beradimi? To'g'ri - qismlarga ajratish.

Nima bo'limga?

Bir qarashda, tanlov aniq - "SHIPMENT_DATE" tugmachasi yordamida "yuborish" jadvalini deklarativ bo'linish (juda oldinga sakrash - oxirida ishlab chiqarishda biroz noto'g'ri chiqdi).

Qanday qilib bo'linish kerak?

Bu savol ham unchalik qiyin emas. Yaxshiyamki, PostgreSQL 10-da endi odamni bo'lish mexanizmi mavjud.
Shunday qilib:

  1. Manba jadvalining axlatini saqlang - pg_dump source_table
  2. Asl jadvalni o'chirish - jadval manba_jadvalini oching
  3. Diapazonga bo'linish bilan ota-jadval yarating - manba_jadvalini yarating
  4. Bo'limlarni yaratish - jadval manba_jadvalini yarating, indeks yarating
  5. 1-bosqichda yaratilgan dumpni import qiling - pg_restore

Bo'lish uchun skriptlar

Oddiylik va qulaylik uchun 2,3,4-bosqichlar bitta skriptga birlashtirildi.

Shunday qilib:
Manba jadvalining axlatini saqlang

pg_dump postgres --file=/dump/shipment.dmp --format=c --table=shipment --verbose > /dump/shipment.log 2>&1

Manba jadvalini o'chiring + Diapazon bo'linishi bilan ota-jadval yarating + Bo'limlarni yarating

--create_partition_shipment.sql
do language plpgsql $$
declare 
rec_shipment_date RECORD ;
partition_name varchar;
index_name varchar;
current_year varchar ;
current_month varchar ;
begin_year varchar ;
begin_month varchar ;
next_year varchar ;
next_month varchar ;
first_flag boolean ;
i integer ;
begin
  RAISE NOTICE 'CREATE TEMPORARY TABLE FOR SHIPMENT_DATE';
  CREATE TEMP TABLE tmp_shipment_date as select distinct "SHIPMENT_DATE" from shipment order by "SHIPMENT_DATE" ;

  RAISE NOTICE 'DROP TABLE shipment';
  drop table shipment cascade ;
  
  CREATE TABLE public.shipment
  (
    "SHIPMENT_ID" integer NOT NULL DEFAULT nextval('shipment_shipment_id_seq'::regclass),
    "SHIPMENT_NAME" character varying(30) COLLATE pg_catalog."default",
    "SHIPMENT_DATE" timestamp without time zone,
    "REPORT_NAME" character varying(40) COLLATE pg_catalog."default"
  )
  PARTITION BY RANGE ("SHIPMENT_DATE")
  WITH (
      OIDS = FALSE
  )
  TABLESPACE pg_default;

  RAISE NOTICE 'CREATE PARTITIONS FOR TABLE shipment';

  current_year:='0';
  current_month:='0';

  begin_year := '0' ;
  begin_month := '0'  ;
  next_year := '0' ;
  next_month := '0'  ;

  FOR rec_shipment_date IN SELECT * FROM tmp_shipment_date LOOP
      
      RAISE NOTICE 'SHIPMENT_DATE=%',rec_shipment_date."SHIPMENT_DATE";
      
      current_year := date_part('year' ,rec_shipment_date."SHIPMENT_DATE");
      current_month := date_part('month' ,rec_shipment_date."SHIPMENT_DATE") ; 

      IF to_number(current_month,'99') < 10 THEN
        current_month := '0'||current_month ; 
      END IF ;

      --Init borders
      IF   begin_year = '0' THEN
       first_flag := true ; --first time flag
       begin_year := current_year ;
       begin_month := current_month ;   
   
        IF current_month = '12' THEN
          next_year := date_part('year' ,rec_shipment_date."SHIPMENT_DATE" + interval '1 year') ;
        ELSE
          next_year := current_year ;
        END IF;
     
       next_month := date_part('month' ,rec_shipment_date."SHIPMENT_DATE" + interval '1 month') ;

      END IF;

      -- Check current date into borders NOT for First time
      IF to_date( current_year||'.'||current_month, 'YYYY.MM') >= to_date( begin_year||'.'||begin_month, 'YYYY.MM') AND 
         to_date( current_year||'.'||current_month, 'YYYY.MM') < to_date( next_year||'.'||next_month, 'YYYY.MM') AND 
         NOT first_flag 
      THEN
         CONTINUE ; 
      ELSE
       --NEW borders only for second and after time 
       begin_year := current_year ;
       begin_month := current_month ;   
   
        IF current_month = '12' THEN
          next_year := date_part('year' ,rec_shipment_date."SHIPMENT_DATE" + interval '1 year') ;
        ELSE
          next_year := current_year ;
        END IF;
     
       next_month := date_part('month' ,rec_shipment_date."SHIPMENT_DATE" + interval '1 month') ;

      END IF;      

      partition_name := 'shipment_shipment_date_'||begin_year||'-'||begin_month||'-01-'|| next_year||'-'||next_month||'-01'  ;
 
     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'  ) ; 

      index_name := partition_name||'_shipment_id_idx';
      RAISE NOTICE 'INDEX NAME =%',index_name;
      EXECUTE format('CREATE INDEX ' || quote_ident(index_name) || ' ON '|| quote_ident(partition_name) ||' USING btree ("SHIPMENT_ID") TABLESPACE pg_default ' ) ; 

      --Drop first time flag
      first_flag := false ;
   
  END LOOP;

end
$$;

Chiqindilarni import qilish

pg_restore -d postgres --data-only --format=c --table=shipment --verbose  shipment.dmp > /tmp/data_dump/shipment_restore.log 2>&1

Bo'lim natijalarini tekshirish

Natijada bizda nima bor? Ijro rejasining to'liq matni katta va zerikarli, shuning uchun o'zingizni yakuniy raqamlar bilan cheklash juda mumkin.

Bu edi

Narxi: 502 997.55
Amalga oshirish vaqti: 505 soniya.

Bo'ldi

Narxi: 77 872.36
Amalga oshirish vaqti: 79 soniya.

Juda yaxshi natija. Qisqartirilgan xarajatlar va bajarish vaqti. Shunday qilib, qismlarga ajratishdan foydalanish kutilgan samarani beradi va umuman, kutilmagan hodisalar yo'q.

Xaridorni xursand qiling

Sinov natijalari mijozga ko'rib chiqish uchun taqdim etildi. Va uni ko'rib chiqqandan so'ng, ularga biroz kutilmagan hukm berildi: "Ajoyib, "ma'lumotlar" jadvalini bo'ling."

Ha, lekin biz butunlay boshqa β€œyuborish” jadvalini koβ€˜rib chiqdik; β€œma’lumotlar” jadvalida β€œSHIPMENT_DATE” maydoni yoβ€˜q.

Muammo yo'q, qo'shing, o'zgartiring. Asosiysi, mijoz natijadan mamnun, amalga oshirish tafsilotlari unchalik muhim emas.

Asosiy jadvalni "ma'lumotlar" ga bo'lish

Umuman olganda, hech qanday maxsus qiyinchiliklar yuzaga kelmadi. Garchi bo'lish algoritmi, albatta, biroz o'zgargan.

β€œSHIPMENT_DATA” ustunini β€œma’lumotlar” jadvaliga qoβ€˜shish

psql -h хост -U Π±Π°Π·Π° -d ΡŽΠ·Π΅Ρ€
=> ALTER TABLE data ADD COLUMN "SHIPMENT_DATE" timestamp without time zone ;

"Ma'lumotlar" jadvalidagi "YUKLASH_DATA" ustunining qiymatlarini "yuborish" jadvalidagi bir xil nomdagi ustun qiymatlari bilan to'ldiring

-----------------------------
--update_data.sql
--updating for altered table "data" to values of "shipment_data" from the table "shipment"
--version 1.0
do language plpgsql $$
declare 
rec_shipment_data RECORD ;
shipment_date timestamp without time zone ; 
row_count integer ;
total_rows integer ;
begin

  select count(*) into total_rows from shipment ; 
  RAISE NOTICE 'Total %',total_rows;
  row_count:= 0 ;

  FOR rec_shipment_data IN SELECT * FROM shipment LOOP

   update data set "SHIPMENT_DATE" = rec_shipment_data."SHIPMENT_DATE" where "SHIPMENT_ID" = rec_shipment_data."SHIPMENT_ID";
   
   row_count:=  row_count +1 ;
   RAISE NOTICE 'row count = % , from %',row_count,total_rows;
  END LOOP;

end
$$;

"Ma'lumotlar" jadvalining axlatini saqlang

pg_dump postgres --file=/dump/data.dmp --format=c --table=data --verbose > /dump/data.log 2>&1</source

Bo'lingan "ma'lumotlar" jadvalini qayta yarating

--create_partition_data.sql
--create partitions for the table "wafer data" by range column "shipment_data" with one month duration
--version 1.0
do language plpgsql $$
declare 
rec_shipment_date RECORD ;
partition_name varchar;
index_name varchar;
current_year varchar ;
current_month varchar ;
begin_year varchar ;
begin_month varchar ;
next_year varchar ;
next_month varchar ;
first_flag boolean ;
i integer ;

begin

  RAISE NOTICE 'CREATE TEMPORARY TABLE FOR SHIPMENT_DATE';
  CREATE TEMP TABLE tmp_shipment_date as select distinct "SHIPMENT_DATE" from shipment order by "SHIPMENT_DATE" ;


  RAISE NOTICE 'DROP TABLE data';
  drop table data cascade ;


  RAISE NOTICE 'CREATE PARTITIONED TABLE data';
  
  CREATE TABLE public.data
  (
    "RUN_ID" integer,
    "LASERMARK" character varying(20) COLLATE pg_catalog."default" NOT NULL,
    "LOTID" character varying(80) COLLATE pg_catalog."default",
    "SHIPMENT_ID" integer NOT NULL,
    "PARAMETER_ID" integer NOT NULL,
    "INTERNAL_VALUE" character varying(75) COLLATE pg_catalog."default",
    "REPORTED_VALUE" character varying(75) COLLATE pg_catalog."default",
    "LOWER_SPEC_LIMIT" numeric,
    "UPPER_SPEC_LIMIT" numeric , 
    "SHIPMENT_DATE" timestamp without time zone
  )
  PARTITION BY RANGE ("SHIPMENT_DATE")
  WITH (
    OIDS = FALSE
  )
  TABLESPACE pg_default ;


  RAISE NOTICE 'CREATE PARTITIONS FOR TABLE data';

  current_year:='0';
  current_month:='0';

  begin_year := '0' ;
  begin_month := '0'  ;
  next_year := '0' ;
  next_month := '0'  ;
  i := 1;

  FOR rec_shipment_date IN SELECT * FROM tmp_shipment_date LOOP
      
      RAISE NOTICE 'SHIPMENT_DATE=%',rec_shipment_date."SHIPMENT_DATE";
      
      current_year := date_part('year' ,rec_shipment_date."SHIPMENT_DATE");
      current_month := date_part('month' ,rec_shipment_date."SHIPMENT_DATE") ; 

      --Init borders
      IF   begin_year = '0' THEN
       RAISE NOTICE '***Init borders';
       first_flag := true ; --first time flag
       begin_year := current_year ;
       begin_month := current_month ;   
   
        IF current_month = '12' THEN
          next_year := date_part('year' ,rec_shipment_date."SHIPMENT_DATE" + interval '1 year') ;
        ELSE
          next_year := current_year ;
        END IF;
     
       next_month := date_part('month' ,rec_shipment_date."SHIPMENT_DATE" + interval '1 month') ;

      END IF;

--      RAISE NOTICE 'current_year=% , current_month=% ',current_year,current_month;
--      RAISE NOTICE 'begin_year=% , begin_month=% ',begin_year,begin_month;
--      RAISE NOTICE 'next_year=% , next_month=% ',next_year,next_month;

      -- Check current date into borders NOT for First time

      RAISE NOTICE 'Current data = %',to_char( to_date( current_year||'.'||current_month, 'YYYY.MM'), 'YYYY.MM');
      RAISE NOTICE 'Begin data = %',to_char( to_date( begin_year||'.'||begin_month, 'YYYY.MM'), 'YYYY.MM');
      RAISE NOTICE 'Next data = %',to_char( to_date( next_year||'.'||next_month, 'YYYY.MM'), 'YYYY.MM');

      IF to_date( current_year||'.'||current_month, 'YYYY.MM') >= to_date( begin_year||'.'||begin_month, 'YYYY.MM') AND 
         to_date( current_year||'.'||current_month, 'YYYY.MM') < to_date( next_year||'.'||next_month, 'YYYY.MM') AND 
         NOT first_flag 
      THEN
         RAISE NOTICE '***CONTINUE';
         CONTINUE ; 
      ELSE
       --NEW borders only for second and after time 
       RAISE NOTICE '***NEW BORDERS';
       begin_year := current_year ;
       begin_month := current_month ;   
   
        IF current_month = '12' THEN
          next_year := date_part('year' ,rec_shipment_date."SHIPMENT_DATE" + interval '1 year') ;
        ELSE
          next_year := current_year ;
        END IF;
     
       next_month := date_part('month' ,rec_shipment_date."SHIPMENT_DATE" + interval '1 month') ;


      END IF;      

      IF to_number(current_month,'99') < 10 THEN
        current_month := '0'||current_month ; 
      END IF ;

      IF to_number(begin_month,'99') < 10 THEN
        begin_month := '0'||begin_month ; 
      END IF ;

      IF to_number(next_month,'99') < 10 THEN
        next_month := '0'||next_month ; 
      END IF ;

      RAISE NOTICE 'current_year=% , current_month=% ',current_year,current_month;
      RAISE NOTICE 'begin_year=% , begin_month=% ',begin_year,begin_month;
      RAISE NOTICE 'next_year=% , next_month=% ',next_year,next_month;

      partition_name := 'data_'||begin_year||begin_month||'01_'||next_year||next_month||'01'  ;

      RAISE NOTICE 'PARTITION NUMBER % , TABLE NAME =%',i , partition_name;
      
      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'  ) ; 

      index_name := partition_name||'_shipment_id_parameter_id_idx';
      RAISE NOTICE 'INDEX NAME =%',index_name;
      EXECUTE format('CREATE INDEX ' || quote_ident(index_name) || ' ON '|| quote_ident(partition_name) ||' USING btree ("SHIPMENT_ID", "PARAMETER_ID") TABLESPACE pg_default ' ) ; 

      index_name := partition_name||'_lasermark_idx';
      RAISE NOTICE 'INDEX NAME =%',index_name;
      EXECUTE format('CREATE INDEX ' || quote_ident(index_name) || ' ON '|| quote_ident(partition_name) ||' USING btree ("LASERMARK" COLLATE pg_catalog."default") TABLESPACE pg_default ' ) ; 

      index_name := partition_name||'_shipment_id_idx';
      RAISE NOTICE 'INDEX NAME =%',index_name;
      EXECUTE format('CREATE INDEX ' || quote_ident(index_name) || ' ON '|| quote_ident(partition_name) ||' USING btree ("SHIPMENT_ID") TABLESPACE pg_default ' ) ; 

      index_name := partition_name||'_parameter_id_idx';
      RAISE NOTICE 'INDEX NAME =%',index_name;
      EXECUTE format('CREATE INDEX ' || quote_ident(index_name) || ' ON '|| quote_ident(partition_name) ||' USING btree ("PARAMETER_ID") TABLESPACE pg_default ' ) ; 

      index_name := partition_name||'_shipment_date_idx';
      RAISE NOTICE 'INDEX NAME =%',index_name;
      EXECUTE format('CREATE INDEX ' || quote_ident(index_name) || ' ON '|| quote_ident(partition_name) ||' USING btree ("SHIPMENT_DATE") TABLESPACE pg_default ' ) ; 

      --Drop first time flag
      first_flag := false ;

  END LOOP;
end
$$;

3-bosqichda yaratilgan dumpni yuklang.

pg_restore -h хост -ΡŽΠ·Π΅Ρ€ -d Π±Π°Π·Π° --data-only --format=c --table=data --verbose  data.dmp > data_restore.log 2>&1

Eski ma'lumotlar uchun alohida bo'lim yarating

---------------------------------------------------
--create_partition_for_old_dates.sql
--create partitions for keeping old dates 
--version 1.0
do language plpgsql $$
declare 
rec_shipment_date RECORD ;
partition_name varchar;
index_name varchar;

begin

      SELECT min("SHIPMENT_DATE") AS min_date INTO rec_shipment_date from data ;

      RAISE NOTICE 'Old date is %',rec_shipment_date.min_date ;

      partition_name := 'data_old_dates'  ;

      RAISE NOTICE 'PARTITION NAME IS %',partition_name;

      EXECUTE format('CREATE TABLE ' || quote_ident(partition_name) || ' PARTITION OF data FOR VALUES FROM ( %L ) TO ( %L )  ' , '1900-01-01' , 
              to_char( rec_shipment_date.min_date,'YYYY')||'-'||to_char(rec_shipment_date.min_date,'MM')||'-01'  ) ; 

      index_name := partition_name||'_shipment_id_parameter_id_idx';
      EXECUTE format('CREATE INDEX ' || quote_ident(index_name) || ' ON '|| quote_ident(partition_name) ||' USING btree ("SHIPMENT_ID", "PARAMETER_ID") TABLESPACE pg_default ' ) ; 

      index_name := partition_name||'_lasermark_idx';
      EXECUTE format('CREATE INDEX ' || quote_ident(index_name) || ' ON '|| quote_ident(partition_name) ||' USING btree ("LASERMARK" COLLATE pg_catalog."default") TABLESPACE pg_default ' ) ; 

      index_name := partition_name||'_shipment_id_idx';
      EXECUTE format('CREATE INDEX ' || quote_ident(index_name) || ' ON '|| quote_ident(partition_name) ||' USING btree ("SHIPMENT_ID") TABLESPACE pg_default ' ) ; 

      index_name := partition_name||'_parameter_id_idx';
      EXECUTE format('CREATE INDEX ' || quote_ident(index_name) || ' ON '|| quote_ident(partition_name) ||' USING btree ("PARAMETER_ID") TABLESPACE pg_default ' ) ; 

      index_name := partition_name||'_shipment_date_idx';
      EXECUTE format('CREATE INDEX ' || quote_ident(index_name) || ' ON '|| quote_ident(partition_name) ||' USING btree ("SHIPMENT_DATE") TABLESPACE pg_default ' ) ; 

end
$$;

Yakuniy natijalar:

Bu edi
Narxi: 502 997.55
Amalga oshirish vaqti: 505 soniya.

Bo'ldi
Narxi: 68 533.70
Amalga oshirish vaqti: 69 soniya

Munosib, munosib. Va shuni hisobga olsak, bu yo'lda biz PostgreSQL 10-da bo'lish mexanizmini ozmi-ko'p o'zlashtirishga muvaffaq bo'ldik - bu ajoyib natija.

Lirik tushunchalar

Bundan ham yaxshiroq qilish mumkinmi - HA, SIZNING MUMKIN!Buning uchun siz MATERIALIZED VIEW dan foydalanishingiz kerak.
MATERIALIZALANGAN KO'RISH LASERMARK_VIEW YARATING

CREATE MATERIALIZED VIEW LASERMARK_VIEW 
AS
SELECT w."LASERMARK" , MAX(s."SHIPMENT_DATE") AS "SHIPMENT_DATE"
FROM shipment s INNER JOIN data w ON s."SHIPMENT_ID" = w."SHIPMENT_ID" 
GROUP BY w."LASERMARK" ;

CREATE INDEX lasermark_vw_shipment_date_ind on lasermark_view USING btree ("SHIPMENT_DATE") TABLESPACE pg_default;
analyze lasermark_view ;

Yana bir bor so'rovni qayta yozamiz:
Moddiylashtirilgan ko'rinish yordamida so'rov

SELECT
            p."PARAMETER_ID" as  parameter_id,
            pc."PC_NAME" AS pc_name,
            pc."CUSTOMER_PARTNUMBER" AS customer_partnumber,
            w."LASERMARK" AS lasermark,
            w."LOTID" AS lotid,
            w."REPORTED_VALUE" AS reported_value,
            w."LOWER_SPEC_LIMIT" AS lower_spec_limit,
            w."UPPER_SPEC_LIMIT" AS upper_spec_limit,
            p."TYPE_CALCUL" AS type_calcul,
            s."SHIPMENT_NAME" AS shipment_name,
            s."SHIPMENT_DATE" AS shipment_date,
            extract(year from s."SHIPMENT_DATE") AS year,
            extract(month from s."SHIPMENT_DATE") as month,
            s."REPORT_NAME" AS report_name,
            p."STC_NAME" AS STC_name,
            p."CUSTOMERPARAM_NAME" AS customerparam_name
        FROM data w INNER JOIN shipment s ON s."SHIPMENT_ID" = w."SHIPMENT_ID"
             INNER JOIN parameters p ON p."PARAMETER_ID" = w."PARAMETER_ID"
             INNER JOIN shipment_pc sp ON s."SHIPMENT_ID" = sp."SHIPMENT_ID"
             INNER JOIN pc pc ON pc."PC_ID" = sp."PC_ID"
             INNER JOIN LASERMARK_VIEW md ON md."SHIPMENT_DATE" = s."SHIPMENT_DATE" AND md."LASERMARK" = w."LASERMARK"
        WHERE 
              s."SHIPMENT_DATE" >= '2018-07-01' AND s."SHIPMENT_DATE" <= '2018-09-30';

Va yana bir natijaga erishamiz:
Bu edi
Narxi: 502 997.55
Amalga oshirish vaqti: 505 soniya

Bo'ldi
Narxi: 42 481.16
Amalga oshirish vaqti: 43 soniya.

Albatta, bunday istiqbolli natija aldamchi bo'lsa ham, g'oyalarni yangilash kerak. Shunday qilib, ma'lumotlarni qabul qilishning umumiy vaqti ko'p yordam bermaydi. Ammo tajriba sifatida bu juda qiziq.

Aslida, ma'lum bo'lishicha, yana bir bor rahmat asmm va Habru! So'rovni yanada yaxshilash mumkin.

So'zdan keyin

Shunday qilib, mijoz mamnun. VA kerak vaziyatdan foydalaning.

Yangi vazifa: Siz chuqurlashtirish va kengaytirish uchun nimani o'ylab topishingiz mumkin?

Va keyin eslayman - bolalar, bizning PostgreSQL ma'lumotlar bazamiz monitoringi yo'q.

AWS-da Cloud Watch ko'rinishida hali ham ba'zi monitoring mavjud. Ammo bu monitoringning DBA uchun qanday foydasi bor? Umuman olganda, deyarli yo'q.

Agar sizda o'zingiz uchun foydali va qiziqarli ish qilish imkoniyati bo'lsa, bu imkoniyatdan foydalana olmaysiz...
UCHUN

Happy Party yoki PostgreSQL10-da bo'linish bilan tanishish haqida bir necha qator xotiralar

Biz eng qiziqarli qismga shunday etib boramiz:

3 yil 2018 dekabr.
PostgreSQL so'rovlarining ishlashini monitoring qilish uchun mavjud imkoniyatlarni o'rganishni boshlash to'g'risida qaror qabul qilish.

Ammo bu butunlay boshqacha hikoya.

Davomi bor…

Manba: www.habr.com

a Izoh qo'shish