Purely declarative FKs

[Thiemo Kellner <thiemo@xxxxxxxxxxxxxxxxxxxx>]

Hi

Please bear with me, if this is the wrong place or this is an old 
question answered over and over again.

Context: In my professional life I rarely come across 
projects/applications where there are foreign keys on the database. This 
is due to loading freedom not due to that there actually were no 
relations. And usually, there is no datamodel. Only the database objects 
have been implemented. So, they end up with a bunch/mess of tables, up 
to your choice, and relations are insider information.

I have read the PostgreSQL documentation on Foreign keys. It seems, that 
it is not possible (easily) to have inactive FKs, so one can have both. 
The relation information on the database at least but the freedom of 
load order/speed at the same time. My short research on the net spoke 
about disabling the trigger used by the FK. If that is possible, this 
would be a way but it feels underhanded to me and I would not have a 
good feeling to do it.

Question: Are there plans to provide a feature in PostgreSQL that one 
can have foreign keys for purely documentation purpose - I know, one 
could use a modelling tool and just not implement the FKs, but my 
reality is, there is hardly ever a modelling tool involved.

Kind regards

Thiemo