Question: what's the difference between making a single index covering
multiple fields of the underlying table, and making a separate index
for each of the fields?
I understand that the semantics are different if I create a UNIQUE
index: a unique index on a field enforces that every record in the table
have a different value of that field, but a unique index on a set of
fields only enforces that the combination of all those fields be unique
in each record.
Leaving that aside, what are the performance implications? Does one
structure support fast execution of query types that the other doesn't,
and if so which one's better for what? Is a single index cheaper to
update than multiple indexes? Does it save disk space?
regards, tom lane
pgsql-sql by date
|Next:||From: Tom Lane||Date: 1998-07-09 16:47:08|
|Subject: Indexes and inheritance (and access rights)|
|Previous:||From: Stephen Horton||Date: 1998-07-09 11:26:00|
|Subject: Newby Postgres questions|