X-Original-To: pgsql-admin-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.144]) by svr1.postgresql.org (Postfix) with ESMTP id 447173A5732 for ; Fri, 3 Dec 2004 13:01:53 +0000 (GMT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 75528-01 for ; Fri, 3 Dec 2004 13:01:32 +0000 (GMT) Received: from curie.credativ.org (credativ.com [217.160.209.18]) by svr1.postgresql.org (Postfix) with ESMTP id 30AE23A56F6 for ; Fri, 3 Dec 2004 13:01:34 +0000 (GMT) Received: from localhost (localhost [127.0.0.1]) by curie.credativ.org (Postfix) with ESMTP id E448255B73; Fri, 3 Dec 2004 14:01:32 +0100 (CET) Received: from www.credativ.de (pD95006C1.dip0.t-ipconnect.de [217.80.6.193]) (using TLSv1 with cipher EDH-RSA-DES-CBC3-SHA (168/168 bits)) (No client certificate requested) by curie.credativ.org (Postfix) with ESMTP id 2C80F55B70; Fri, 3 Dec 2004 14:01:32 +0100 (CET) Received: from bell.credativ.de (bell.credativ.de [172.26.14.16]) by www.credativ.de (Postfix) with ESMTP id E82331C0044; Fri, 3 Dec 2004 14:01:28 +0100 (CET) From: Peter Eisentraut To: =?iso-8859-1?q?M=AA_Jos=E9_Sempere?= Subject: Re: binary tipes Date: Fri, 3 Dec 2004 14:01:19 +0100 User-Agent: KMail/1.6.2 Cc: References: <000301c4d932$3c02dfb0$0900a8c0@mj> In-Reply-To: <000301c4d932$3c02dfb0$0900a8c0@mj> MIME-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 8bit Message-Id: <200412031401.19775.peter_e@gmx.net> X-Virus-Scanned: by AMaViS at credativ.com X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0.05 tagged_above=0 required=5 tests=FORGED_RCVD_HELO X-Spam-Level: X-Archive-Number: 200412/33 X-Sequence-Number: 15619 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/