3 ms·
Kind of glossed over the whole "CREATE INDEX CONCURRENTLY" thing in the "Table Changes" section, no?
by mattdeboard 12y ago
Kind of glossed over the whole "CREATE INDEX CONCURRENTLY" thing in the "Table Changes" section, no?
- masklinn 12y ago"table change" looks to be changes to the table's data since it only mentions table or row locking. If it were about schema change, I don't think there's any way to talk the result into a tie, that's really one of the things MySQL is absolutely terrible at.
- arenaninja 12y agoSee, things like these should've been in that article. The rest of it was "everything is a tie except for JOINs but they've been working fine in MySQL since 5.6.5 so I chose Postgres". I've personally suffered through hours of deployment in a legacy MySQL application with a few million records. Thanks for this tidbit, I'm that much more curious about Postgres now
- lsaferite 12y agoYeah, the fact the DDL statements are transactionable in Postgres is a HUGE win IMHO.