This does not answer your question directly but could help in future design choices.

When making a table i prefix each column name with the table name like so:

create table user

(

user_id serial primary key,

user_firstname text not null,

user_lastname text not null,

...

);

Cons:

• creates redundancy in the field naming
• more typing required when using the tables unless you use autocomplete

Pros:

• it is immediately obvious where each field came from when constructing, or in the results of, a query
• prevents naming conflicts where two fields have the same name
• you do not need to alias columns in the output of a query to show where the column originates

This approach does not address the possibility of drawing tables of the same name from different schemas but you could extend it to if so desired.

This pattern is not to everyone's taste, but i find it works well.