Heh I actually went the opposite way as it made my database schemas more difficult. If it's a one-on-one with just one piece of data, make it an extra column in

Heh I actually went the opposite way as it made my database schemas more difficult. If it's a one-on-one with just one piece of data, make it an extra column instead (sometimes I've also done this for many-to-ones if there is only some small but neglegible data duplication going on). One reason I do use one-on-ones is when the column is heavy on updates, because on update PostgreSQL rewrites the entire row.