Last active
December 11, 2015 17:28
-
-
Save pvh/4634543 to your computer and use it in GitHub Desktop.
Postgres: The Bits You Haven't Found talk
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
| A Beastiary of Badassery | |
| - | |
| SQLisms | |
| -- | |
| WITH | |
| arrays and unnest | |
| window functions | |
| JSON | |
| row types | |
| selects in the target list | |
| full-text search | |
| range types | |
| reading EXPLAIN | |
| exclusion constraints | |
| LISTEN/NOTIFY | |
| intervals and time | |
| generate_series | |
| CASE WHEN pivots | |
| coalesce | |
| Extensia | |
| -- | |
| hstore | |
| dblink | |
| uuid-ossp | |
| pgcrypto | |
| tablefunc? | |
| pl/v8 | |
| postgis | |
| pppppsql! | |
| -- | |
| \d*+ | |
| \i | |
| \e | |
| \x | |
| URL support | |
| Performance/Operations | |
| -- | |
| CONCURRENTLY | |
| GIN/GIST | |
| knn | |
| application_name | |
| pg_stat_activity | |
| pg_stat_statements | |
| pg_locks | |
| pg_statio | |
| pg_cancel_backend | |
| sync commit | |
| pg_stat_replication | |
| Index only scans | |
| BONUS ROUND | |
| - | |
| 9.3's a comin' | |
| lateral joins | |
| SUPERJSON | |
| foreign data wrappers (more than french hip-hop) | |
| background (database!) workers | |
| (other?) |
From CK: \pset null, already found it handy - craigkerstiens.com/2013/02/21/mor… and +1 to \set [alias] [query]
The \set commands can be used not just for full queries. I use to save some that ended with something like 'where order_id = ' and would then run it with something like :order 2342523; Worked great.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
When talking about interval and time handling, don't forget to emphasize how Postgres magically does the right thing with interval arithmetic in the face of timezones, DST, etc. Apparently that is a real differentiator, and I think it nicely illustrates the general Postgres ethos of putting a lot of effort into getting these details right, so the user doesn't have to.
inet types that have many operators (including bitwise operators), so you can do arithmetic with them, and calculate appropriate bitmasks. You could also have declarative constraints enforced using them.
fuzzystrmatch is kind of interesting, though I'm not sure it should make the cut.
Partially indexes. This is something that Instagram use extensively. Maybe mention create index concurrently in passing.