From: | Stephan Szabo <sszabo(at)megazone(dot)bigpanda(dot)com> |
---|---|
To: | Jaime Casanova <systemguards(at)yahoo(dot)com> |
Cc: | pgsql-admin(at)postgresql(dot)org |
Subject: | Re: unique constraints on foreign keys |
Date: | 2004-09-20 23:27:50 |
Message-ID: | 20040920162457.D84638@megazone.bigpanda.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin pgsql-general |
On Mon, 20 Sep 2004, Jaime Casanova wrote:
> --- Stephan Szabo <sszabo(at)megazone(dot)bigpanda(dot)com>
> escribi:
> >
> > On Mon, 20 Sep 2004, Jaime Casanova wrote:
> >
> > > There is a way to not enforce the creation of a
> > > primary or unique index on a referenced table?
> >
> > Not really. It's not the index that's important
> > per-se, it's the uniqueness that is implied.
>
> OK. What about to teach the planner always do a
> seq on that table and do not ask for use the
> index? but not using "set" instructions. can i do
> that?
Not really. Are you worried about the cost of doing the plan analysis for
the index scan or that it might choose to actually use the index?
Theoretically, it's only going to currently plan the fk scan on status
once per connection because that plan should be saved.
From | Date | Subject | |
---|---|---|---|
Next Message | Robert Treat | 2004-09-21 06:20:35 | Re: Postgres setup question |
Previous Message | Jaime Casanova | 2004-09-20 23:18:52 | Re: unique constraints on foreign keys |
From | Date | Subject | |
---|---|---|---|
Next Message | Mark Harrison | 2004-09-21 00:13:30 | Re: using database for queuing operations? |
Previous Message | Jaime Casanova | 2004-09-20 23:18:52 | Re: unique constraints on foreign keys |