Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
Showing
1 changed file
with
38 additions
and
0 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,38 @@ | ||
# Is Postgres the future of Open SQL # | ||
|
||
## by Harold Giménez ## | ||
|
||
### Abstract ### | ||
|
||
Most ruby and Rails :tm: developers use an SQL database | ||
to let their objects rest until they're needed again. | ||
Oftentimes, this database is Postgres. | ||
|
||
This talk will arm you with general knowledge to be used | ||
to more efficiently utilize PostgreSQL to fulfill your | ||
application's OLTP load and reporting. | ||
|
||
Basically what are some amazing postgres features that make it so sweet, | ||
and a bit of history on the project. It covers: | ||
|
||
* How postgres does durability | ||
* How you as a user can balance between durability and performance | ||
* Advanced query constructs: CTEs, Window functions in particular | ||
* Advanced data types | ||
* Advanced indexing techniques | ||
* Extensions and how/why it's the future of databases | ||
* How postgres handles concurrency and how you can control that | ||
|
||
You will leave this talk with a sampling of what features are | ||
available to you from Postgres when you hit your next | ||
complex data needs. | ||
|
||
### Additional Notes ### | ||
|
||
I haven't had Dunkin' Donuts coffee in a while :coffee: | ||
|
||
## Social ## | ||
|
||
* [http://practiceovertheory.com](blog) | ||
* [http://twitter.com/hgmnz](@hgmnz) | ||
* [https://github.com/hgmnz](GitHub) |