postgresql - Audit Table DB Design : Does creating Audit Tables for Join Tables make sense -

We are creating separate audit tables for those unit tables, which require auditing by using triggers on PostgreSQL 8.4 is.

  & lt; Family & gt; & Lt; Contacts & gt; & Lt; Family_Contact & gt; & Lt; Address & gt;  

We have a few tables. Example: Family_Contact is an included table.

The family has 1 or more 1 contact. Each contact has an address, therefore, we have the following table structure.

For auditing a family, we need the following tables which are duplicates of the above tables.

  & lt; Family_audit & gt; & Lt; Contact_audit & gt; & Lt; Family_Contact_audit & gt; & Lt; Address_audit & gt;  

Family_Contact_audit is an AUDIT insert table.

Question: What is the meaning of creating a separate audit table for the inclusion table? What are the options? We will use Audit Tables for reporting purposes.

Thank you,

Yes, they still make sense.

You can not track changes made in family contact without the audit table in that specific table.

I do not see any other way to track changes and usage without making these tables separate.