Received: from localhost (unknown [200.46.204.183])
	by postgresql.org (Postfix) with ESMTP id CDDF765049F
	for <pgsql-performance-postgresql.org@postgresql.org>;
	Sat, 26 Jul 2008 18:51:29 -0300 (ADT)
Received: from postgresql.org ([200.46.204.86])
	by localhost (mx1.hub.org [200.46.204.183]) (amavisd-maia, port 10024)
	with ESMTP id 96590-01-3
	for <pgsql-performance-postgresql.org@postgresql.org>;
	Sat, 26 Jul 2008 18:51:21 -0300 (ADT)
X-Greylist: domain auto-whitelisted by SQLgrey-1.7.6
Received: from rv-out-0506.google.com (rv-out-0506.google.com
 [209.85.198.226])
	by postgresql.org (Postfix) with ESMTP id 7864F650432
	for <pgsql-performance@postgresql.org>;
	Sat, 26 Jul 2008 18:48:53 -0300 (ADT)
Received: by rv-out-0506.google.com with SMTP id b25so4741906rvf.43
	for <pgsql-performance@postgresql.org>;
	Sat, 26 Jul 2008 14:48:51 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma;
	h=domainkey-signature:received:received:message-id:date:from:sender
	:to:subject:cc:in-reply-to:mime-version:content-type:references
	:x-google-sender-auth;
	bh=oFBERpPdnCISNC+11h6lW45yQNiyBX6jIXCv9863X4c=;
	b=AfjAwLRu3TuA62DpAsRqQHjdRkBIHKyDs+OMxdgjja00MF5XRm0CqF6LPPT29aBUNL
	4FC4o3QEHP0gq2GJ6xuJCnb9sxa7a2xfsAagDIQ7/IA/JwNFfMAp5K5lOIw/mK/SLWkR
	OhZx8FKsxK5tNWt00U+HZ0xySjBDngLiMrtsU=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma;
	h=message-id:date:from:sender:to:subject:cc:in-reply-to:mime-version
	:content-type:references:x-google-sender-auth;
	b=VXqqhwTKzEr9onZmc01zojRvyWY6L6jKXid4umQcM4OCrXVlM9ZxhuHlMECwX/KtrK
	eewTlOyMBXUgG4Z46sFiJKawPoS6/V3TOqLVpO+1dSSe27O2pzy530jEa6Au/j44YsoI
	SH62CAd4Rsq/tumq5akWxkqqWJJNvrZPfxB4Y=
Received: by 10.141.170.10 with SMTP id x10mr1589999rvo.105.1217108930897;
	Sat, 26 Jul 2008 14:48:50 -0700 (PDT)
Received: by 10.140.177.2 with HTTP; Sat, 26 Jul 2008 14:48:50 -0700 (PDT)
Message-ID: <c6bf5b380807261448h65aac228i112cdca380bf4b4@mail.gmail.com>
Date: Sat, 26 Jul 2008 23:48:50 +0200
From: "David Andersen" <david@andersen.gs>
To: "Tom Lane" <tgl@sss.pgh.pa.us>
Subject: Re: Using ENUM with huge NAMEDATALEN
Cc: pgsql-performance@postgresql.org
In-Reply-To: <4191.1217108664@sss.pgh.pa.us>
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_Part_2617_13326182.1217108930895"
References: <c6bf5b380807261422i77ed5b3evf55da6891e2e4170@mail.gmail.com>
	<4191.1217108664@sss.pgh.pa.us>
X-Google-Sender-Auth: 36f3adfc80b62a84
X-Virus-Scanned: Maia Mailguard 1.0.1
X-Spam-Status: No, hits=0.001 tagged_above=0 required=5
	tests=HTML_MESSAGE=0.001
X-Spam-Level: 
X-Archive-Number: 200807/229
X-Sequence-Number: 30829

------=_Part_2617_13326182.1217108930895
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

Hi Tom,

Thanks a lot for the tip! I will try this. You probably saved be a few days
of work!

Regards,

David

On Sat, Jul 26, 2008 at 11:44 PM, Tom Lane <tgl@sss.pgh.pa.us> wrote:

> "David Andersen" <david@andersen.gs> writes:
> > One of the side tables is text with length of up to 900 characters. My
> > question is whether I could build PostgreSQL with NAMEDATALEN  (which
> > controls the max size of Enums) equal to 900?
>
> I wouldn't recommend it.  Consider changing pg_enum.enumlabel to type
> TEXT instead.
>
>                        regards, tom lane
>
>
>

------=_Part_2617_13326182.1217108930895
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

<div dir="ltr">Hi Tom,<br><br>Thanks a lot for the tip! I will try this. You probably saved be a few days of work!<br><br>Regards,<br><br>David<br><br><div class="gmail_quote">On Sat, Jul 26, 2008 at 11:44 PM, Tom Lane <span dir="ltr">&lt;<a href="mailto:tgl@sss.pgh.pa.us">tgl@sss.pgh.pa.us</a>&gt;</span> wrote:<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><div class="Ih2E3d">&quot;David Andersen&quot; &lt;<a href="mailto:david@andersen.gs">david@andersen.gs</a>&gt; writes:<br>

&gt; One of the side tables is text with length of up to 900 characters. My<br>
&gt; question is whether I could build PostgreSQL with NAMEDATALEN &nbsp;(which<br>
&gt; controls the max size of Enums) equal to 900?<br>
<br>
</div>I wouldn&#39;t recommend it. &nbsp;Consider changing pg_enum.enumlabel to type<br>
TEXT instead.<br>
<br>
 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;regards, tom lane<br>
<br>
<br>
</blockquote></div><br></div>

------=_Part_2617_13326182.1217108930895--