From: | Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com> |
---|---|
To: | ginkgo36 <ginkgo56(at)gmail(dot)com>, pgsql-general(at)postgresql(dot)org |
Subject: | Re: :Posgres - performance problem |
Date: | 2015-03-25 14:43:28 |
Message-ID: | 5512C990.8000209@aklaver.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On 03/25/2015 07:30 AM, ginkgo36 wrote:
> @Gary
> I'm working on big data, because of the demands of the job so I
> export/import/update data on this table every day.
>
> I guess it's possible that each query would need all 417 columns but it
> seems unlikely... --> Yes, not at all but 2/3 of 417 columns :)
There is also the matter of the 34 indexes, which can thought of as 34
axillary tables that need to be kept in sync with the main table.
>
> I need gather data into one table for consistency and easy for export and
> import, it's ok if I split data to smaller tables, but when
> export/import/update, i must excute query on alot of table. And this way
> lead data to inconsistency if I forget update/export/import on 1 or more
> table. It is terrible.
>
>
> @John
>
> I will learing about it. Thanks alot.
>
> @All: If you have any suggestion, please let me known. Thanks for you help
>
>
>
--
Adrian Klaver
adrian(dot)klaver(at)aklaver(dot)com
From | Date | Subject | |
---|---|---|---|
Next Message | Adrian Klaver | 2015-03-25 14:51:26 | Re: Postgresql 9.5 |
Previous Message | YBarot | 2015-03-25 14:36:57 | Postgresql 9.5 |