Re: INSERT/SELECT and excessive foreign key checks

From: Andrew Dunstan <andrew(at)dunslane(dot)net>
To: James Mansion <james(at)mansionfamily(dot)plus(dot)com>
Cc: Gregory Stark <stark(at)enterprisedb(dot)com>, Lodewijk Voege <lvoege(at)gmail(dot)com>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: INSERT/SELECT and excessive foreign key checks
Date: 2007-08-19 21:50:05
Message-ID: 46C8BB0D.9000005@dunslane.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

James Mansion wrote:
> I was wondering whether one could try to identify what might be termed
> 'enum tables' that exist to provide lookups.
>
> There are perhaps three main types of table that is the target of a
> foreign key lookup:
>
> 1) tables that map to program language enumerations: typically small
> (less than a hundred rows) and changing very infrequently.
>
>

8.3's enum types will help with these, and they get you out of the FK
game altogether.

cheers

andrew

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Andrew Dunstan 2007-08-20 01:41:44 Re: [PATCHES] COPYable logs
Previous Message Gregory Stark 2007-08-19 18:39:32 Re: INSERT/SELECT and excessive foreign key checks