Skip site navigation (1) Skip section navigation (2)

Re: constraint with reference to the same table

From: "Victor Yegorov" <viy(at)nordlb(dot)lv>
To: Rudi Starcevic <rudi(at)oasis(dot)net(dot)au>
Cc: Postgres Performance <pgsql-performance(at)postgresql(dot)org>
Subject: Re: constraint with reference to the same table
Date: 2003-05-15 00:12:39
Message-ID: 20030515001239.GC1549@nordlb.lv (view raw or flat)
Thread:
Lists: pgsql-performance
* Rudi Starcevic <rudi(at)oasis(dot)net(dot)au> [15.05.2003 02:59]:
> Hi,
> 
> Can I confirm what this means then ..
> 
> For large table's each column with ref. inegritry I should create an 
> index on those columns ?

I think, that indicies are needed only at delete stage to decrease search
time of possible referencing rows.
Not only, of course, but when we speak about
INSERT/UPDATE/DELETE data it is so.

On the other side, indicies increases total query runtime, because for
each row deleted/updated/inserted it'll be necessary to update each index.

In my case, I at first drop "cyclic" constraints, do the job and then
restore them.


-- 

Victor Yegorov

In response to

Responses

pgsql-performance by date

Next:From: Stephan SzaboDate: 2003-05-15 00:46:47
Subject: Re: constraint with reference to the same table
Previous:From: Rudi StarcevicDate: 2003-05-15 00:07:34
Subject: Re: constraint with reference to the same table

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group