Postgres ENUM data type or CHECK CONSTRAINT?

Question

I have been migrating a MySQL db to Pg (9.1), and have been emulating MySQL ENUM data types by creating a new data type in Pg, and then using that as the column definition. My q

Answer 1

From my point of view, given a same set of values

1. Enum is a better solution if you will use it on multiple column
2. If you want to limit the values of only one column in your application, a check constraint is a better solution.

Of course, there is a whole lot of other parameters which could creep in your decision process (typically, the fact that builtin operators are not available), but I think these two are the most prevalent ones.