Re: [Bizgres-general] Re: A Guide to Constraint

From: Hannu Krosing <hannu(at)tm(dot)ee>
To: Simon Riggs <simon(at)2ndquadrant(dot)com>
Cc: Richard Huxton <dev(at)archonet(dot)com>, bizgres-general(at)pgfoundry(dot)org, pgsql-hackers(at)postgresql(dot)org
Subject: Re: [Bizgres-general] Re: A Guide to Constraint
Date: 2005-07-13 20:31:54
Message-ID: 1121286714.5551.9.camel@fuji.krosing.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On K, 2005-07-13 at 16:10 +0100, Simon Riggs wrote:
> On Wed, 2005-07-13 at 14:02 +0100, Richard Huxton wrote:
> > Sounds very useful - even for my small systems. Does it/would it work on
> > an ordinary table (for those cases currently using UNION ALL)?
>
> I'm looking into that aspect right now.
>
> I see no reason why it shouldn't work for UNION ALL views/queries in the
> same manner as it does for inheritance.

Why does the CE speed depend on having index on pg_inherits ?

Can't you just check the constraints on individual tables ?

Or are the constraints not actually copied to child tables, and you must
look them up from parent tabless ?

--
Hannu Krosing <hannu(at)tm(dot)ee>

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Victor Yegorov 2005-07-13 20:33:52 Determine index's attribute number by scankey
Previous Message Alvaro Herrera 2005-07-13 20:23:08 Re: checkpoint_segments 32 megs?