| From: | Bruno Wolff III <bruno(at)wolff(dot)to> |
|---|---|
| To: | frank(at)joerdens(dot)de |
| Cc: | Guy Rouillier <guyr(at)masergy(dot)com>, PostgreSQL General <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: Debugging deadlocks |
| Date: | 2005-04-01 13:57:00 |
| Message-ID: | 20050401135700.GB26112@wolff.to |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Fri, Apr 01, 2005 at 10:37:11 +0200,
frank(at)joerdens(dot)de wrote:
>
> And idea that just came up around here that sounds like a pretty neat
> workaround, which we're gonna try, is to drop the foreign key
> constraints, and just use a check constraint for the allowed values. If
> the cardinality of the reference table is small, this is much faster
> than using foreign keys and solves your problem. With the drawback that
> if you update the reference table (if you keep it), you mustn't forget
> to also update the check constraints in more than one place.
Using domains is a good way to keep column constraints in just one place.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruno Wolff III | 2005-04-01 14:00:34 | Re: FW: Help with order by into a RECORD |
| Previous Message | Jaqui Greenlees | 2005-04-01 13:39:48 | Re: [Fwd: [webmaster] in Search of free hosting with PostgreSQL] |