Re: [PERFORM] Query taking long time

2014-03-20 Thread acanada
Hello, New server postgres version is 9.3. I'm not sure if I collected latest statistics after migration, if you mean if the current_settings or analyze queries that I posted were collected after migration... yes (notice that there are analyze query before migration and after migration, maybe I

Re: [PERFORM] Adding new field to big table

2014-03-17 Thread acanada
th=18) (6 rows) It's not using the index, most of the rows are beeing updated. I'm trying with the CTAS solution. Cheers, Andrés. El Mar 14, 2014, a las 8:29 PM, Jeff Janes escribió: > On Fri, Mar 14, 2014 at 10:06 AM, acanada wrote: > Hello Jeff, > > The lock time is no

Re: [PERFORM] Adding new field to big table

2014-03-14 Thread acanada
s El Mar 14, 2014, a las 5:49 PM, Jeff Janes escribió: > On Fri, Mar 14, 2014 at 4:30 AM, acanada wrote: > Hello, > > I'm having time issues when adding new fields to a big table. I hope you can > point me some hints to speed up the updates of a table with 124 million >

[PERFORM] Adding new field to big table

2014-03-14 Thread acanada
Hello, I'm having time issues when adding new fields to a big table. I hope you can point me some hints to speed up the updates of a table with 124 million rows... This is what I do: First I create a tmp_table with the data that will be added to the big table: \d+ svm_confidence_id_tmp

Re: [PERFORM] Query taking long time

2014-03-11 Thread acanada
nf 94M , > but how much it's big ? it's important the average row length > > > Have a nice day > > 2014-03-06 15:45 GMT+01:00 acanada : > Hello Mat, > > Setting enable_bitmapscan to off doesn't really helps. It gets worse... > >

Re: [PERFORM] Query taking long time

2014-03-10 Thread acanada
:134217724 413088 133804636 Thank you for your help, Andrés El Mar 10, 2014, a las 3:45 PM, Evgeniy Shishkin escribió: > > On 07 Mar 2014, at 13:18, acanada wrote: > >> The table entity2document2 has 30GB. In consecutive runs it gets much >> better... 30ms ap

Re: [PERFORM] Query taking long time

2014-03-07 Thread acanada
El Mar 7, 2014, a las 11:03 AM, Evgeniy Shishkin escribió: > > On 07 Mar 2014, at 12:46, acanada wrote: > >> >> El Mar 7, 2014, a las 10:39 AM, Evgeniy Shishkin escribió: >> >>> >>>> Hello Mat, >>>> >>>> Setting enab

Re: [PERFORM] Query taking long time

2014-03-07 Thread acanada
;>>> >>>> We need to look for other possible work around. Please drop off the above >>>> Index. Let me see if i can drill further into this. >>>> >>>> Meanwhile - can you help us know the memory parameters (work_mem, >>>> temp_buffers

Re: [PERFORM] Query taking long time

2014-03-06 Thread acanada
7;s performance ? > > > > Any info about your Disk, RAM, CPU would also help. > > > > Regards, > > Venkata Balaji N > > > > Fujitsu Australia > > > > > > > > > > Venkata Balaji N > > > > Sr. Database Administrator &g

Re: [PERFORM] Query taking long time

2014-03-04 Thread acanada
ctual time=35.174..35.174 rows=138165 loops=1) Index Cond: ((name)::text = 'progesterone'::text) Total runtime: 95811.838 ms (8 rows) Any ideas please? Thank you Andrés. El Mar 4, 2014, a las 12:28 AM, Venkata Balaji Nagothi escribió: > On Mon, Mar 3, 2014 at 9:1

Re: [PERFORM] Query taking long time

2014-03-04 Thread acanada
for this table are: tablename | attname | n_distinct entity_compounddict2document | name | 16635 entity_compounddict2document | hepval | 2.0e+06 Thank you very much for your help!! Andrés El Mar 4, 2014, a las 12:28 AM, Venkata Balaji Nagothi escribió: > On Mon

Re: [PERFORM] Query taking long time

2014-02-27 Thread acanada
y" on documentold d1_ (cost=0.00..22.04 rows=1 width=254) (actual time=21.747..21.764 rows=1 loops=3170) Index Cond: (d1_.id = e0_.document_id) Filter: (d1_.hepval IS NOT NULL) Total runtime: 80556.027 ms Any help/point to any direction, would be

[PERFORM] Query taking long time

2014-02-26 Thread acanada
Hello to everybody and thanks in advance to take a look to this message. I'm new in this list and with PostgreSQL. My queries are taking too much time to complete and I don't know what to do right now. I think I'm providing all the info required for you to help me. If you need extra info please