Re: [GENERAL] :Posgres - performance problem

2015-03-26 Thread Marc Mamin
> update master_items set "feedback_to_de" = 'Yes' >--Query returned successfully: 591268 rows affected, 1589335 ms execution time. Here you should better use update master_items set feedback_to_de = 'Yes' WHERE feedback_to_de <> 'Yes' OR update master_items set feedback_to_de <> 'Yes' WHERE fee

Re: [GENERAL] :Posgres - performance problem

2015-03-25 Thread John R Pierce
On 3/25/2015 2:19 AM, ginkgo36 wrote: Hi all, I have 1 table have: - 417 columns - 600.000 rows data - 34 indexs when i use query on this table, it so long. ex: update master_items set temp1 = '' where temp1 <> '' --Query returned successfully: 435214 rows affected, 1016137 ms execution time.

Re: [GENERAL] :Posgres - performance problem

2015-03-25 Thread lucas.g...@gmail.com
"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 terri

Re: [GENERAL] :Posgres - performance problem

2015-03-25 Thread Adrian Klaver
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

Re: [GENERAL] :Posgres - performance problem

2015-03-25 Thread Raymond O'Donnell
On 25/03/2015 14:30, 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 c

Re: [GENERAL] :Posgres - performance problem

2015-03-25 Thread ginkgo36
@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 :) I need gather data into one table for

Re: [GENERAL] :Posgres - performance problem

2015-03-25 Thread lucas.g...@gmail.com
I'm not an expert either, but your data model sounds very broken as well... I guess it's possible that each query would need all 417 columns but it seems unlikely... If that were normalized into 'n' tables then each query would be returning a whole lot less data... I've never heard of a database

Re: [GENERAL] :Posgres - performance problem

2015-03-25 Thread John McKown
On Wed, Mar 25, 2015 at 4:19 AM, ginkgo36 wrote: > Hi all, > I have 1 table have: > - 417 columns > - 600.000 rows data > - 34 indexs > > when i use query on this table, it so long. ex: > > update master_items set > temp1 = '' where temp1 <> '' --Query returned successfully: 435214 rows > affected

[GENERAL] :Posgres - performance problem

2015-03-25 Thread ginkgo36
Hi all, I have 1 table have: - 417 columns - 600.000 rows data - 34 indexs when i use query on this table, it so long. ex: update master_items set temp1 = '' where temp1 <> '' --Query returned successfully: 435214 rows affected, 1016137 ms execution time. alter table master_items add "TYPE-DE"