Author(s):	Craig Kerstiens
Location	Auditorium
Date	feb Sun 23	Days Raw Files
Start	11:05	First Raw Start	error-in-template
Duration	00:35:00	Offset	None
End	11:40	Last Raw End
Chapters
Total cuts_time	None min.

http://pytennessee.org/schedule/presentation/9/
raw-playlist raw-mp4-playlist encoded-files-playlist mp4 svg png

assets release.pdf Postgres_Performance_for_Humans.json
logs
Admin: episode episode list cut list raw files day marks day marks day image_files

State:	--------- borked edit encode push to queue post richard review 1 email review 2 make public tweet to-miror conf done
Locked:	clear this to unlock
Locked by:	user/process that locked.
Start:	initially scheduled time from master, adjusted to match reality
Duration:	length in hh:mm:ss
Name:	Video Title (shows in video search results)
Emails:	email(s) of the presenter(s)
Released:	Unknown Yes No has someone authorised pubication
Normalise:
Channelcopy:	m=mono, 01=copy left to right, 10=right to left, 00=ignore.
Thumbnail:	filename.png
Description:	To many developers the database is a black box. You expect to be able to put data into your database, have it to stay there, and get it out when you query it... hopefully in a performant manner. We'll walk through a bit of a clearer guide of how you can understand how database is doing from a 30,000 foot perspective as well as analyze specific problematic queries and how to tune them. markdown
Comment:	production notes