From: Kynn Jones <kynnjo@gmail.com>
To: Heikki Linnakangas <heikki@enterprisedb.com>
Cc: pgsql-performance@postgresql.org
Subject: Re: The "many nulls" problem
Date: Fri, 14 Mar 2008 16:05:20 -0400
Message-ID: <c2350ba40803141305s286c7ec9n4dff5c60f3f3b035@mail.gmail.com> (raw)
In-Reply-To: <47DAD5F8.6060804@enterprisedb.com>
References: <c2350ba40803141105o1d2a9a30o60f5108b2fc15f1@mail.gmail.com>
<47DAD5F8.6060804@enterprisedb.com>
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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-performance@postgresql.org
Cc: kynnjo@gmail.com, heikki@enterprisedb.com
Subject: Re: The "many nulls" problem
In-Reply-To: <c2350ba40803141305s286c7ec9n4dff5c60f3f3b035@mail.gmail.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox