News for hackers. Stuff that matters.
Re:MySQL vs PostgreSQL by sbov on Wednesday August 15, 2012 @07:25PM (#4388922)
Depending upon its definition, you can add a column to a PostgreSQL table without locking it.

Maybe they changed it in later versions of MySQL, but adding a column to a table become so lengthy for some of our projects that we switched for that reason alone.

Re:MySQL vs PostgreSQL by boyter on Wednesday August 15, 2012 @07:44PM (#4389041)
Its one of the big reasons I am looking at switching. I have been dumping the table and reloading it in using a new name and the renaming the tables to get around this issue but its hardly ideal.
Re:MySQL vs PostgreSQL by einhverfr on Wednesday August 15, 2012 @09:16PM (#4389382)
What's funny is I used to use MySQL for db prototyping because altering schemas on PostgreSQL was such a pain (prior to 7.3). Now it is much better.
Re:MySQL vs PostgreSQL by AaronBBrown on Thursday August 16, 2012 @04:00PM (#4393372)
pt-online-schema-change should resolve that issue for you: http://www.percona.com/doc/percona-toolkit/2.1/pt-online-sch...
Re:MySQL vs PostgreSQL by boyter on Thursday August 16, 2012 @06:19PM (#4393955)
Seems the risks are such my approch works just as well,

"pt-online-schema-change modifies data and structures. You should be careful with it, and test it before using it in production. You should also ensure that you have recoverable backups before using this tool."

With that being the case what im doing is fine I guess.

Re:MySQL vs PostgreSQL by AaronBBrown on Friday August 17, 2012 @09:36PM (#4399830)
Because there is a disclaimer, you are disregarding a thoroughly tested product that solves your exact problem? One which is released by one of the premier MySQL consultancies with the author of "the" MySQL book as the designer?
Re:MySQL vs PostgreSQL by boyter on Monday August 20, 2012 @05:41AM (#4406859)
I don't pay for support. So yes.
Re:MySQL vs PostgreSQL by AaronBBrown on Monday August 20, 2012 @07:18AM (#4407039)
You could make the same exact disclaimer about SQL statement and it would be true:

"INSERT modifies data and structures. You should be careful with it, and test it before using it in production. You should also ensure that you have recoverable backups before using this tool."

"ALTER modifies data and structures. You should be careful with it, and test it before using it in production. You should also ensure that you have recoverable backups before using this tool."

It's just good advice to test stuff before you use it in production. Discarding an awesome product simply because the authors (responsibly) mention that you should probably test it out seems overly paranoid and would severely limit your choices. Percona Toolkit is the most well known and reliable set of tools out there in the MySQL ecosystem.

Re:MySQL vs PostgreSQL by GrumpySimon on Wednesday August 15, 2012 @09:12PM (#4389361)
What are you doing that you need to alter your schema so often?!
Re:MySQL vs PostgreSQL by boyter on Wednesday August 15, 2012 @10:24PM (#4389611)
Its not that I do it often, its how long it takes. An alter on a 60 gig table takes hours, during which your table is locked which is totally unacceptable.
Re:MySQL vs PostgreSQL by therico on Thursday August 16, 2012 @08:35AM (#4390858)
It's a pity your team didn't come across pt-online-schema-change. It's been extremely useful for our large migrations.