Received: from localhost (unknown [200.46.204.183])
	by postgresql.org (Postfix) with ESMTP id 5AC992E036F
	for <pgsql-performance-postgresql.org@postgresql.org>;
	Fri, 14 Mar 2008 17:05:25 -0300 (ADT)
Received: from postgresql.org ([200.46.204.71])
	by localhost (mx1.hub.org [200.46.204.183]) (amavisd-maia, port 10024)
	with ESMTP id 75808-02 for
	<pgsql-performance-postgresql.org@postgresql.org>;
	Fri, 14 Mar 2008 17:05:22 -0300 (ADT)
X-Greylist: domain auto-whitelisted by SQLgrey-1.7.5
Received: from rn-out-0910.google.com (rn-out-0910.google.com
 [64.233.170.188])
	by postgresql.org (Postfix) with ESMTP id 104132E0369
	for <pgsql-performance@postgresql.org>;
	Fri, 14 Mar 2008 17:05:21 -0300 (ADT)
Received: by rn-out-0910.google.com with SMTP id e11so2566649rng.17
	for <pgsql-performance@postgresql.org>;
	Fri, 14 Mar 2008 13:05:20 -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:to:subject:cc:in-reply-to:mime-version:content-type:references;
	bh=E+en+YI4IWxLdeHpniNQjNy9ptDrtIiG3HZR06zCNuQ=;
	b=IpaSgXE6y3MRK70N5L3QMYFplHg8YnBP4mazr64OqH+GtLWH8uVzEL2AHoMPlv3kcgebeMbZN16S/m4fzowbcyYnGt6U2ZNtptw4wFej0SuYt1z5uQcoaNqcV8RloY9oRfRG4Xj6jc85mw2/ytokmWvTU37Wf4cWsMyDG6QIQgg=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma;
	h=message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:references;
	b=XUVRpzpEr7TnZ5dBKam6k50S/pVn58DQnRem/LXew7oxa/jTi6RTjo8DmR3WAZgNL6+6RgZLwhHlYSo5mVmmI7ORmQh6BVe1b1OcK0vl8yH/baD4hiE4eTRBgvmqJPQjSVsdEXmI9xY48AAp3Q94cNET2garCZKYT617K+11zYI=
Received: by 10.114.76.1 with SMTP id y1mr12602149waa.38.1205525120126;
	Fri, 14 Mar 2008 13:05:20 -0700 (PDT)
Received: by 10.114.109.16 with HTTP; Fri, 14 Mar 2008 13:05:20 -0700 (PDT)
Message-ID: <c2350ba40803141305s286c7ec9n4dff5c60f3f3b035@mail.gmail.com>
Date: Fri, 14 Mar 2008 16:05:20 -0400
From: "Kynn Jones" <kynnjo@gmail.com>
To: "Heikki Linnakangas" <heikki@enterprisedb.com>
Subject: Re: The "many nulls" problem
Cc: pgsql-performance@postgresql.org
In-Reply-To: <47DAD5F8.6060804@enterprisedb.com>
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_Part_2324_3258634.1205525120098"
References: <c2350ba40803141105o1d2a9a30o60f5108b2fc15f1@mail.gmail.com>
	<47DAD5F8.6060804@enterprisedb.com>
X-Virus-Scanned: Maia Mailguard 1.0.1
X-Archive-Number: 200803/316
X-Sequence-Number: 29270

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

On Fri, Mar 14, 2008 at 3:46 PM, Heikki Linnakangas <heikki@enterprisedb.com>
wrote:
>
> <tons of useful info snipped>
>
 From performance point of view, I would go with a single table with
> NULL fields on PostgreSQL.


Wow.  I'm so glad I asked!  Thank you very much!

Kynn

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

<div class="gmail_quote">On Fri, Mar 14, 2008 at 3:46 PM, Heikki Linnakangas &lt;<a href="mailto:heikki@enterprisedb.com">heikki@enterprisedb.com</a>&gt; wrote:<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div class="Ih2E3d">&lt;tons of useful info snipped&gt;&nbsp;</div></blockquote><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;"><div class="Ih2E3d"></div>&nbsp;From performance point of view, I would go with a single table with<br>

NULL fields on PostgreSQL.</blockquote><div><br class="webkit-block-placeholder"></div><div>Wow. &nbsp;I&#39;m so glad I asked! &nbsp;Thank you very much!</div><div><br class="webkit-block-placeholder"></div><div>Kynn</div><div>&nbsp;</div>
</div>

------=_Part_2324_3258634.1205525120098--