PostgreSQL as a Schemaless Database.

Recommendations

Info

Some Conclusions, 2. • Avoid doing full-table scans if you need to use an accessor function. • Although hstore’s are not bad compared to xpath or a PL. • Seriously consider hstore if you have the flexibility. • It’s really fast.
Flame Bait! • MongoDB doesn’t seem to be more performant than PostgreSQL. • And you still get all of PostgreSQL’s goodies. • Larger documents will probably continue to favor PostgreSQL. • As will larger tables.
Page 1 and 2:
PostgreSQL as a Schemaless Database
Page 3 and 4:
What’s on the menu? • What is a
Page 5 and 6:
Schematic. • A schema is a fixed
Page 7 and 8: We are not amused. • Culturally,
Page 9 and 10: What is schemaless data? • Schema
Page 11 and 12: XML It seemed like a good idea at t
Page 13 and 14: XML, your dad’s document language
Page 15 and 16: XML Support in PostgreSQL. • Buil
Page 17 and 18: hstore The hidden gem of contrib/
Page 19 and 20: hstore functions • Lots and lots
Page 21 and 22: JSON All the cool kids are doing it
Page 23 and 24: JSON, the new hotness • The de fa
Page 25 and 26: JSON Indexing. • Expression index
Page 27 and 28: PL/V8 ProTips • Use the static V8
Page 29 and 30: CREATE OR REPLACE FUNCTION get_json
Page 31 and 32: But but but… • PostgreSQL was n
Page 33 and 34: Schemaless Shootout! • A very bas
Page 35 and 36: Timing Harness. • Scripts written
Page 37 and 38: Indexing Philosophy • For relatio
Page 39 and 40: The Sophisticated Database Tuning P
Page 41 and 42: 6000 4500 3000 1500 0 Records/Secon
Page 43 and 44: Next Test: Disk Footprint. • Fina
Page 45 and 46: Observations. • GIN indexes are r
Page 47 and 48: 400 300 200 100 0 Fetch Time in Mil
Page 51 and 52: Next Test: Query on Name • For a
Page 55 and 56: Observations. • GiST and GIN acce
Page 57: Some Conclusions. • PostgreSQL do
Page 61: Thank you! thebuild.com @xof
show all

PostgreSQL as a Schemaless Database.

Create successful ePaper yourself

Delete template?

Save as template?