| From: | Scott Marlowe <scott(dot)marlowe(at)gmail(dot)com> |
|---|---|
| To: | Miguel Angel Conte <diafano(at)gmail(dot)com> |
| Cc: | Kevin Crain <kevin(dot)crain1(at)gmail(dot)com>, pgsql-sql(at)postgresql(dot)org |
| Subject: | Re: Max column number. |
| Date: | 2011-07-13 16:51:06 |
| Message-ID: | CAOR=d=27Kj2ws2Ho_ZYkTuxDRoPyMg8S6FBjp5h1hHo5BYJXHw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-sql |
On Wed, Jul 13, 2011 at 9:45 AM, Miguel Angel Conte <diafano(at)gmail(dot)com> 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.
This definitely sounds like a job for something like hstore.
Also, can you drop and recreate the table every so often? That would
certainly help.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Miguel Angel Conte | 2011-07-13 17:57:56 | Re: Max column number. |
| Previous Message | Reinoud van Leeuwen | 2011-07-13 15:53:55 | Re: Max column number. |