| From: | Arnaud Lesauvage <arnaud(dot)listes(at)codata(dot)eu> |
|---|---|
| To: | tv(at)fuzzy(dot)cz |
| Cc: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: UPDATE with JOIN not using index |
| Date: | 2010-03-16 15:11:05 |
| Message-ID: | 4B9F9F89.6050604@codata.eu |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Le 16/03/2010 16:02, tv(at)fuzzy(dot)cz a écrit :
>> I will try increasing work_mem, but it is already set at 16MB which I
>> found is quite high.
>
> What do you mean by "high"? I believe the proper value of work_mem is such
> that results in highest performance of the query while not causing
> problems to the other sessions.
Yes, that's true, see my answer below.
> Don't forget you can set this for each session separately (SET work_mem =
> something) so you can use some conservative value in the postgresql.conf
> and use a different value (e.g. 64MB) for batch processing. I guess you
> don't perform such UPDATE in usual sessions, right?
Indeed, I did NOT know that I could set work_mem for each session !
That makes a big difference actually !
I'll try this ASAP !
Thanks a lot for the hint !
Regards,
Arnaud
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alvaro Herrera | 2010-03-16 15:11:59 | Re: Daylight savings time confusion |
| Previous Message | Arnaud Lesauvage | 2010-03-16 15:08:51 | Re: UPDATE with JOIN not using index |