X-Original-To: pgsql-admin-postgresql.org@postgresql.org Received: from localhost (mx1.hub.org [200.46.208.251]) by postgresql.org (Postfix) with ESMTP id 72E8B9FB209 for ; Thu, 27 Jul 2006 18:09:14 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.208.251]) (amavisd-new, port 10024) with ESMTP id 54814-10 for ; Thu, 27 Jul 2006 18:09:08 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey- Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130]) by postgresql.org (Postfix) with ESMTP id 83ABF9FB214 for ; Thu, 27 Jul 2006 18:08:38 -0300 (ADT) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.13.6/8.13.6) with ESMTP id k6RL8bPP008568; Thu, 27 Jul 2006 17:08:37 -0400 (EDT) To: "Daniel Caune" cc: pgsql-admin@postgresql.org Subject: Re: Index row maximum size and crash In-reply-to: <1E293D3FF63A3740B10AD5AAD88535D202B64D40@UBIMAIL1.ubisoft.org> References: <1E293D3FF63A3740B10AD5AAD88535D202B64D40@UBIMAIL1.ubisoft.org> Comments: In-reply-to "Daniel Caune" message dated "Thu, 27 Jul 2006 15:30:19 -0400" Date: Thu, 27 Jul 2006 17:08:36 -0400 Message-ID: <8567.1154034516@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=0.036 tagged_above=0 required=5 tests=AWL, SPF_HELO_PASS, SPF_PASS, UPPERCASE_25_50 X-Spam-Level: X-Archive-Number: 200607/244 X-Sequence-Number: 22490 "Daniel Caune" writes: > I try to create an index on character varying(64) column but PostgreSQL > complains that the index row size reaches the maximum limit: > CREATE INDEX IDX_GSLOG_EVENT_ARCHIVE_GAME_CLIENT_VERSION > ON GSLOG_EVENT_ARCHIVE(GAME_CLIENT_VERSION); > ERROR: index row requires 198468548 bytes, maximum size is 8191 That sure looks like a corrupted-data problem. Have you checked for bad data in the GAME_CLIENT_VERSION column? regards, tom lane