From Startup to Mature Company: PostgreSQL Tips and techniques
0 likes158 views
The document discusses tips and techniques for PostgreSQL databases, emphasizing the importance of data relationships, designing databases according to client language, and the use of timestamps and stored procedures for efficient database management. It also highlights best practices such as keeping records updated and the significance of a well-structured workflow. Additionally, it touches on technical aspects, including building models, managing data efficiently, and promoting documentation for better understanding.
![JSON
jashmead@nistica.com 16
response = {
"result": "OK",
"number_of_serials": 3,
"message": "We found three
serials",
"serials": [ "SN1", "SN2",
"SN3" ],
"details": {
"retrieved_on": "2018-01-01
03:17:04",
"length": 1003
}
}
•Compact
•Easy to
read
•Native in
PostgreSQL
•Frozen
JavaScript](https://image.slidesharecdn.com/tipsandtechniquesnistica8-180402005535/85/From-Startup-to-Mature-Company-PostgreSQL-Tips-and-techniques-16-320.jpg)
From Startup to Mature Company: PostgreSQL Tips and techniques
- 2. ÊWavelength Selective Switches (WSS)☑ Agile Optical Networks 2 MSAN 10Gbà 100Gb LOCAL HD DISTRIBUTION IPDSLAM IPDSLAM Data Center Access Metro Edge Metro Core Long-Haul ** Æ Ê Ê ☑ ☑ ☑ ☑ CRITICAL BUILDING BLOCKS à AGILE OPTICAL NETWORKS Tunable Pluggable Lasers * Optical Channel Monitors (OCM) Agile Optical Networks ☑ ☑
- 3. 3 INPUT EXPRESS DROP 1x2 WSS 1) Automated routing of individual channels – Reconfigurable Optical Add-Drop Mux (ROADM) 2) Dynamic channel power management – Allows long distance transmission 3) Integrated optical channel monitoring – Information feedback for power management Wavelength Selective Switch (WSS)
- 4. What is a Zeppelin? jashmead@nistica.com 4 •Manufacturing Database •Drives manufacture via automated checklists •Work flow management •Training checks •Module data •Customer datasheets •Process engineering
- 5. Checklist Manifesto • Getting the basics right • Every time • In ICU, 5 steps to insert line • Infection rate from 11% to 0 jashmead@nistica.com 5
- 6. How to design a database • Listen to the client talk about their business • Where they use nouns, use tables. • Where they use verbs, use functions. • Turn their adjectives into columns, • and their adverbs into the parameters for the functions. jashmead@nistica.com 6
- 7. It’s about the relationships • Like nouns, tables only valuable in combination • Foreign keys • Bones and tendons • Documentation • Performance jashmead@nistica.com 7
- 8. Keys are primary • Anonymous • Natural keys • Sequences • Fast enough for temp tables • And can set ranges in useful ways jashmead@nistica.com 8 CREATE SEQUENCE serials_id_seq START WITH 1000000000 INCREMENT BY 1 MINVALUE 1000000000 MAXVALUE 1249999999 CACHE 1;
- 9. Timestamps — Or where on the planet are we? jashmead@nistica.com 9
- 10. Time to pull the trigger • Timestamps • Keep scope limited • Complex validation • History • Error trapping jashmead@nistica.com 10 CREATE TRIGGER serials_timestamp BEFORE UPDATE ON serials FOR EACH ROW EXECUTE PROCEDURE timestamp_trg();
- 11. CREATE FUNCTION timestamp_trg() RETURNS trigger LANGUAGE plpgsql AS $$ begin /* force timestamps -- created_at & updated_at fields exist -- set Model.record_timestamps = false; -- this keeps ActiveRecord from trying to do the update */ if new.created_at is null then new.created_at = now(); end if; new.updated_at = now(); return new; end; $$; Stored Procedures - Muscles of a Database jashmead@nistica.com 11
- 12. Staying true to type •Rich type system •Induced types •Defined domains •Conversions •General functions jashmead@nistica.com 12 CREATE FUNCTION sn_process(sn0 sn_t, stuff description_t) LANGUAGE plpgsql AS $$ declare sn1 sn_t; serial_id1 serials.id %type; top_serial_id1 serials.id%type; begin
- 13. Metadata jashmead@nistica.com 13 select a.attname from pg_catalog.pg_attribute a, pg_catalog.pg_class c, pg_catalog.pg_namespace n where a.attrelid = c.oid and c.relnamespace = n.oid and c.relname = ? and n.nspname = 'public' and a.attnum > 0 -- gets rid of internal columns and a.attisdropped = 'f' order by a.attnum
- 15. It’s about the conversation jashmead@nistica.com 15 •KISS •Separation of concerns •DRY •Right tool •Local standards
- 16. JSON jashmead@nistica.com 16 response = { "result": "OK", "number_of_serials": 3, "message": "We found three serials", "serials": [ "SN1", "SN2", "SN3" ], "details": { "retrieved_on": "2018-01-01 03:17:04", "length": 1003 } } •Compact •Easy to read •Native in PostgreSQL •Frozen JavaScript
- 17. Crash reporting • No exceptions • Be specific • Leave log entry • Notify IT • Tell the user what to do next jashmead@nistica.com 17
- 18. Death to Yellow Stickies jashmead@nistica.com 18
- 19. Start with the help jashmead@nistica.com 19
- 20. I have a syncing feeling about this… •Hub & spokes •Technical problems •Push model •Positive verification required! jashmead@nistica.com 20
- 21. 2B or Not 2B •Engineering DB in SQL Server •2B or Not 2B •LATIN1 •Different organization jashmead@nistica.com 21
- 22. Some Assembly Required •Parts in assembly travel together •But when you pull part out? •And move it back? •Some thought required! jashmead@nistica.com 22 Start in Vietnam Go to NJ Replace Sub-assembly Ship Back to Vietnam
- 24. What next? • Blogs • User groups • Email list • Books • Reference manuals jashmead@nistica.com 24