X-Original-To: pgsql-performance-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.144]) by svr1.postgresql.org (Postfix) with ESMTP id 888043A60B9 for ; Thu, 27 Jan 2005 22:07:23 +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 21146-02 for ; Thu, 27 Jan 2005 22:07:19 +0000 (GMT) Received: from wproxy.gmail.com (wproxy.gmail.com [64.233.184.197]) by svr1.postgresql.org (Postfix) with ESMTP id 6B0C73A6085 for ; Thu, 27 Jan 2005 22:07:19 +0000 (GMT) Received: by wproxy.gmail.com with SMTP id 40so300451wri for ; Thu, 27 Jan 2005 14:07:19 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:references; b=KJWA2c3XfAVxTm2Y+bBkvgNt9Bam7nP+jNeXmMUIttFgUe9w0UeLulspjuCRkWYLlqgHNraH74GfZUGUKNVppAeuvyS7B6K0TKQUREFvxuRUA87dJv5NdKWVpP4/xnXAJfO+M/bvxd99CpE/XOFWuTTQwiF5cTDEg9gItpT+g8Y= Received: by 10.54.20.25 with SMTP id 25mr46307wrt; Thu, 27 Jan 2005 14:07:19 -0800 (PST) Received: by 10.54.20.47 with HTTP; Thu, 27 Jan 2005 14:07:19 -0800 (PST) Message-ID: <1dc7f0e3050127140746eeb3e7@mail.gmail.com> Date: Thu, 27 Jan 2005 17:07:19 -0500 From: Alexandre Leclerc Reply-To: Alexandre Leclerc To: Merlin Moncure Subject: Re: Flattening a kind of 'dynamic' table Cc: PERFORM In-Reply-To: <6EE64EF3AB31D5448D0007DD34EEB3412A75F4@Herge.rcsinc.local> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit References: <6EE64EF3AB31D5448D0007DD34EEB3412A75F4@Herge.rcsinc.local> X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0.024 tagged_above=0 required=5 tests=RCVD_BY_IP X-Spam-Level: X-Archive-Number: 200501/558 X-Sequence-Number: 10248 On Thu, 27 Jan 2005 16:05:09 -0500, Merlin Moncure wrote: > Alexandre wrote: > > like I'm doing right now, that "de-normalizing" in an array is the way > > to go. > > Only sometimes. Looping application code is another tactic. There may > be other things to do as well that don't involve arrays or application > code. Consider arrays a (very postgresql specific) tool in your > expanding toolchest. I take good notes of that. All this opened to me other ways for solutions, so I'm glad of that. I'll take more time to think about all that. > De-normalization is a loaded term because we are only presenting queried > data in an alternate format (normalization normally applying to data > structured within the database). There are many people on this list who > will tell you not to de-normalize anything, ever (and most of the time, > you shouldn't!). Thank you for all you help and time for this. Best regards. -- Alexandre Leclerc