| From: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
|---|---|
| To: | Mª José Sempere <mjose(at)pixelart(dot)es> |
| Cc: | <pgsql-admin(at)postgresql(dot)org> |
| Subject: | Re: binary tipes |
| Date: | 2004-12-03 13:01:19 |
| Message-ID: | 200412031401.19775.peter_e@gmx.net |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
Am Freitag, 3. Dezember 2004 13:18 schrieb Mª José Sempere:
> We've created a table with a bytea type field.
> We'd like having no more than one row with identical content
> In that field. So, we've declared a unique index on that field.
> We'd like to know if in tables with a lot of rows the existence of that
> index will slow the insertion of new rows
Yes.
> (perhaps because before inserting
> it must compare that field with the content of the same bytea field
> For all the existing rows in the table).
Not with all rows, since it's a B-tree index, but with some rows for sure.
> We'd also like to know how does PostgreSql implement that comparation
> Between bytea fields (if it compares all the content of the field,
Yes.
--
Peter Eisentraut
http://developer.postgresql.org/~petere/
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2004-12-03 16:13:18 | Re: On disk format postgresql 7.4.3-i386 and x86-64 ? |
| Previous Message | Mª José Sempere | 2004-12-03 12:18:43 | binary tipes |