From: | "Roberto Caravani" <JFanatiker(at)gmx(dot)at> |
---|---|
To: | pgsql-novice(at)postgresql(dot)org |
Subject: | unique constraint |
Date: | 2012-04-17 17:46:26 |
Message-ID: | 20120417174626.10610@gmx.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-novice |
Hi!
I have a little problem with a unique constraint:
create table meta_data (
id serial primary key,
type int not null,
data bytea not null,
unique (type, data)
);
data can be quite large (a few hundred kilo bytes). The unique constraint automatically creates a btree index as I learned from the documentation. The problem is that I get an error when inserting data, that the index is to large. I would like to keep the unique constraint, is there a way to fix this?
I googled the problem and found others having similar issues, but I have not found a solution that suited me.
Thanks in advance!
Best regards,
Robert
--
NEU: FreePhone 3-fach-Flat mit kostenlosem Smartphone!
Jetzt informieren: http://mobile.1und1.de/?ac=OM.PW.PW003K20328T7073a
From | Date | Subject | |
---|---|---|---|
Next Message | ktm@rice.edu | 2012-04-17 19:16:02 | Re: unique constraint |
Previous Message | Chetan Suttraway | 2012-04-17 07:28:14 | Re: Partitioned tables and triggers |