tbicr

5 ms·

1. 1.▲
   Wisdom of the crowd Python web frameworks rank(github.com)

   4 points by tbicr 5y ago|0 comments
2. 2.▲
   New Postgres 12 SET NOT NULL constraint creation with minimal lock

   1 points by tbicr 7y ago|0 comments
3. 3.▲
   by tbicr 8y ago

   Unfortunately savepoints live only in transaction and ACCESS EXCLUSIVE will be released only on whole transaction commit/rollback, so look like no benefits with savepoints for schema migrations to compare with plain transaction.
4. 4.▲
   by tbicr 8y ago

   Constraints creation also tricky because in transaction it take ACCESS EXCLUSIVE lock (eg. lock table on READ/WRITE) and spend time to constraint validation (CHECK, NOT NULL, FOREIGN KEY), so lock will be released only on transaction c
5. 5.▲
   by tbicr 8y ago

   I found only two caveats: - it doesn't use transactions, so if migration will down, then you will need to fix state manually (one point of improvement), however you cannot run `CREATE INDEX CONCURRENTLY` in transaction. - it can use `C
6. 6.▲
   Django zero-downtime migrations for Postgres that respect database locks(github.com)

   122 points by tbicr 8y ago|34 comments