SERIAL is the PostgreSQL version. Right now, the Arc code creates its own ids. It will have to be changed to assume auto-increment. And yes, we may, eventually. We also need primary and foreign key constraints, not null constraints, indices, and other things. I plan to add all those after the initial conversion and the live app is pulling from SQL. Having zero constraints initially makes the conversion faster, which is important because I plan to bring hubski down to convert. Right now, it takes about an hour. I could do it live, but that would take extra code, and an hour downtime at 04:00 CDT is acceptable. If you're referring to 'search_text' etc when you say 'reference tables,' those will be going away when the real search solution is done. None of the other one-to-many tables will be very big. I'm also on the fence about auto-increment. I'm not primarily a database dev, but as a developer, I generally disapprove of logic in databases. But that's a different argument.