News for hackers. Stuff that matters.
Re:Twitter's UID associated to each tweet will very soon exc... by fleaflicker on Tuesday June 09, 2009 @10:24AM (#649118)
That command will take several hours to complete and write lock the table.
Re:Twitter's UID associated to each tweet will very soon exc... by Andys on Tuesday June 09, 2009 @09:31PM (#650368)
Unless you use PostgreSQL.

But then you would have had 64 bit ID by default anyway.

Re:Twitter's UID associated to each tweet will very soon exc... by jsonscripter on Tuesday June 09, 2009 @11:34AM (#649245)
Why can't you just redirect the writes to a new temporary table and join the original and temporary on reads? (I'm not a database admin)
Re:Twitter's UID associated to each tweet will very soon exc... by karanbhangui on Tuesday June 09, 2009 @01:28PM (#649445)
I'm actually interested in this answer as well. I know of a company using a proprietary db and now that their growth has literally exploded, they're stuck with it.
Re:Twitter's UID associated to each tweet will very soon exc... by jsonscripter on Tuesday June 09, 2009 @02:47PM (#649632)
I wonder what literally exploding growth looks like...
Re:Twitter's UID associated to each tweet will very soon exc... by blhack on Tuesday June 09, 2009 @03:11PM (#649706)
Re:Twitter's UID associated to each tweet will very soon exc... by TweedHeads on Tuesday June 09, 2009 @11:00AM (#649189)
Nothing the fail whale can't fix ;-)