Received: from maia.hub.org (maia-5.hub.org [200.46.204.29]) by mail.postgresql.org (Postfix) with ESMTP id E21C2B5DC49 for ; Wed, 13 Jul 2011 12:54:07 -0300 (ADT) Received: from mail.postgresql.org ([200.46.204.86]) by maia.hub.org (mx1.hub.org [200.46.204.29]) (amavisd-maia, port 10024) with ESMTP id 85427-04 for ; Wed, 13 Jul 2011 15:54:01 +0000 (UTC) X-Greylist: from auto-whitelisted by SQLgrey-1.7.6 Received: from smtp-vbr15.xs4all.nl (smtp-vbr15.xs4all.nl [194.109.24.35]) by mail.postgresql.org (Postfix) with ESMTP id 606DFB5DC44 for ; Wed, 13 Jul 2011 12:54:01 -0300 (ADT) Received: from spoetnik.xs4all.nl (spoetnik.xs4all.nl [82.95.228.65]) by smtp-vbr15.xs4all.nl (8.13.8/8.13.8) with ESMTP id p6DFrtrr098859 for ; Wed, 13 Jul 2011 17:54:00 +0200 (CEST) (envelope-from reinoud.v@n.leeuwen.net) Received: by spoetnik.xs4all.nl (Postfix, from userid 1000) id 998361CC5A; Wed, 13 Jul 2011 17:53:55 +0200 (CEST) Date: Wed, 13 Jul 2011 17:53:55 +0200 From: Reinoud van Leeuwen To: pgsql-sql@postgresql.org Subject: Re: Max column number. Message-ID: <20110713155355.GU1984@spoetnik.xs4all.nl> Mail-Followup-To: pgsql-sql@postgresql.org References: <20110712175238.GJ1984@spoetnik.xs4all.nl> <20110712211240.GK1984@spoetnik.xs4all.nl> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.13 (2006-08-11) X-Virus-Scanned: by XS4ALL Virus Scanner X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=-1.9 tagged_above=-5 required=5 tests=BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001 X-Spam-Level: X-Archive-Number: 201107/62 X-Sequence-Number: 35632 On Wed, Jul 13, 2011 at 12:45:45PM -0300, Miguel Angel Conte wrote: > Hi, > > Thanks for your interest. This app load scv files which change every day > (sometimes the columns too). The sizes of these files are in avg 15MB. So, > We load something like 100MB each day. We tried to find a better solution > but we couldn't, becouse one of the our requirement is not to use a lot of > space. Also, the app is used to consult these information, and for our > particular type of select's queries, we get the best performance if the > information is all into a same row. Still, you could normalize the data in a better way, and present it to users or an application with views or stored procedures... Reinoud -- __________________________________________________ "Nothing is as subjective as reality" Reinoud van Leeuwen reinoud.v@n.leeuwen.net http://reinoud.van.leeuwen.net kvk 27320762 __________________________________________________