6 ms·
One of the creators here. We'd love feedback on the screencasts and suggestions on topics that you'd like to see covered!
by jbranchaud 10y ago
One of the creators here.
We'd love feedback on the screencasts and suggestions on topics that you'd like to see covered!
- mhd 10y agoLateral Joins Recursive Queries (+ generating JSON from them) Advanced Index Types (Ab-)using arrays & custom types (contrast with JSON(B) for everything)
- dkarter 10y agoWe just finished recording a new episode about Lateral Joins it will be the next episode (early next week). Thanks for your feedback!
- insertnickname 10y agoIs there a feed? I'd much rather have a feed than an e-mail newsletter.
- ing33k 10y agoNice ! request : can you do some screencasts on window functions ?
- saurabh 10y ago+1
- sudhirj 10y agoCTEs, window functions, JSONB, PostGIS, and other stuff I wouldn't have heard of or learnt otherwise :)
- kevindeasis 10y agoPostGIS would be amazing. Followed by JsonB. Then migrating from JsonB to relational. Hot standby might be interesting too.
- juliangoldsmith 10y ago+1 on PostGIS.
- kirang1989 10y ago+1 for JsonB.
- madawan 10y ago+1 for administration (esp. hot stand-by).
- humanfromearth 10y agoEpisode suggestion: VARCHAR vs TEXT
- paulmd 10y agoPretty easy to get just from reading the first couple paragraphs of the documentation. Postgres has three string types, CHARACTER, CHARACTER VARYING, and TEXT. CHARACTER VARYING is the basic type of string, and can be given with a maximum character length. If no length is given, the max value is assumed. CHARACTER is a padded string - all strings are padded to the specified length with spaces. If no length is given, the length 1 is assumed. TEXT is an alias for a CHARACTER VARYING without a length parameter (max length). Actually all string types are handled the same internally, and there's no performance reason to use CHARACTER instead of CHARACTER VARYING. In fact it may hurt performance since the padding increases the data size. Using length constraints also carries a slight performance hit during writes as the constraint gets checked. https://www.postgresql.org/docs/9.5/static/datatype-character.html https://www.postgresql.org/docs/9.5/static/datatype-characte...
- andruby 10y agoHot standby. How to promote a slave to master. Continuous archiving. Effective logging and analysing with eg. PgBadger. Performance tuning and benchmarking. Best practices around those tasks would really be helpful.
- teddyh 10y agoPrimary keys: INTEGER, BIGINT or UUID?
- philliphaydon 10y agoHiLo
- teddyh 10y agoFor those who don’t know what it is: https://vladmihalcea.com/2014/06/23/the-hilo-algorithm/ https://vladmihalcea.com/2014/06/23/the-hilo-algorithm/ Basically, it optimizes for lots of insert operations by using a composite primary key, one of which is a SERIAL assigned by the server, and the other is a value arbitrarily assigned by the client. This allows a client to assign and use many new unique keys without asking the server for a new value for every individual row.
- jbranchaud 10y agoand natural keys!
- dagw 10y agoWorking with raster data
- kyriakos 10y agoThis is a great idea. Thanks. PostgreSQL is a very complicated and feature rich system but has a steep learning curve once you deviate from the basic CRUD. Even though the documentation is decent its not very beginner friendly - hopefully the screencasts will grow in number and topics to help make Postgre more mainstream.
- kriro 10y agoA screencast on using PG to handle stuff that is often stored in noSQL databases would be interesting. I'd be interested in both using PG's new noSQL capabilities but more importantly also in walking through creating a Schema for the data (and the tradeoffs). I'd suggest mining some Tweets with metadata from the streaming API (JSON) and using that as a running example.
- graffitici 10y ago1 !
- deathtrader666 10y agoSetting up PostgreSQL for a REST API ?
- boothead 10y agoAre you aware of http://postgrest.com/ http://postgrest.com/?
- abhimskywalker 10y agoThanks! Was not aware if this is even possible. This looks quite awesome!
- snuxoll 10y agoIt is quite awesome. It'd be even more awesome if it had support for kerberos (and delegation) built in so I didn't have to write an external JWT provider, if I could rely on PostgreSQL's built-in kerberos support for authentication it would be amazing.
- MasterYoda 10y agoSecurity is always important. So would be nice with a guide how to setup pg securly.
- madmulita 10y ago+1
- NatW 10y agoA very detailed breakdown of the basics of 'explain analyze' with various examples.
- fleetfox 10y agoReading and understanding EXPLAINS and planner, FTS.
- Dangeranger 10y agoPlease create an episode about creating custom functions, especially aggregation functions using PL/pgSQL
- Dangeranger 10y agoPlease talk about database views, both regular and materialized. When they are best used, strengths and weaknesses. Compare composing a combined query out of CTE's and sub-queries.
- evv555 10y agoEdge cases of jsonb queries and best practices.
- paulmd 10y agoClustering/horizontally scaling Postgres. This is one of the toughest topics with Postgres IMO.
- nek4life 10y agoI'd love to see a tutorial for JSONB to be used as an alternative to an EAV model or a hybrid approach.