Re: How are foreign key constraints built? - Mailing list pgsql-general

From Alvaro Herrera
Subject Re: How are foreign key constraints built?
Date
Msg-id 20050123214536.GG19315@dcc.uchile.cl
Whole thread Raw
In response to Re: How are foreign key constraints built?  ("Jim C. Nasby" <decibel@decibel.org>)
Responses Re: How are foreign key constraints built?  ("Jim C. Nasby" <decibel@decibel.org>)
List pgsql-general
On Sun, Jan 23, 2005 at 03:19:10PM -0600, Jim C. Nasby wrote:

> > People have this weird notion that an index-based plan is always faster
> > than anything else.  If you like you can try the operation with "set
> > enable_seqscan = off", but I bet it will take longer.
>
> Well, every other database I've used can do index covering, which means
> index scans *are* faster.

... on those database systems.  Indexes are different in Postgres in
general: they don't have visibility info (other systems don't need it,
tuples are always visible), and in some databases you have clustered
indexes, where the index is also the heap.

--
Alvaro Herrera (<alvherre[@]dcc.uchile.cl>)
"We are who we choose to be", sang the goldfinch
when the sun is high (Sandman)

pgsql-general by date:

Previous
From: "Jim C. Nasby"
Date:
Subject: Re: How are foreign key constraints built?
Next
From: "Jim C. Nasby"
Date:
Subject: Re: How are foreign key constraints built?