This did fix my problem. I thought that it was a constraint because
the error message I got said that the action was violating the unique
constraint. I didn't realize until later that actually meant the
unique constraint on the index,
I'd be interested in the question here, as well.
Carol
On May 6, 2009, at 1:45 AM, Michael Monnerie wrote:
On Dienstag 05 Mai 2009 Tom Lane wrote:
Apparently this is just an index, not a constraint (the difference
being that it was made with CREATE INDEX, not ALTER TABLE ADD
CONSTRAINT). Try
Is there a performance difference? Or is it just a matter of taste
which
one you use? Technically, are they both indices, or is the
constraint a
check that's executed on insert/update, but doesn't store the values?
mfg zmi
--
// Michael Monnerie, Ing.BSc ----- http://it-management.at
// Tel: 0660 / 415 65 31 .network.your.ideas.
// PGP Key: "curl -s http://zmi.at/zmi.asc | gpg --import"
// Fingerprint: AC19 F9D5 36ED CD8A EF38 500E CE14 91F7 1C12 09B4
// Keyserver: wwwkeys.eu.pgp.net Key-ID: 1C1209B4
--
Sent via pgsql-admin mailing list (pgsql-admin@xxxxxxxxxxxxxx)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-admin
--
Sent via pgsql-admin mailing list (pgsql-admin@xxxxxxxxxxxxxx)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-admin
