From: | "Fernando Hevia" <fhevia(at)ip-tel(dot)com(dot)ar> |
---|---|
To: | "'Richard Neill'" <rn214(at)cam(dot)ac(dot)uk> |
Cc: | <pgsql-performance(at)postgresql(dot)org> |
Subject: | Re: Postgres query completion status? |
Date: | 2009-11-20 21:32:07 |
Message-ID: | AB1925220F644A5D887758FB10398986@iptel.com.ar |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-performance |
> -----Mensaje original-----
> De: Richard Neill
>
> Fernando Hevia wrote:
> >
> >
> >> -----Mensaje original-----
> >> De: Richard Neill
> >>
> >>
> >> max_connections = 500 # (change requires restart)
> >> work_mem = 256MB # min 64kB
> >
> > Not that it has to do with your current problem but this
> combination
> > could bog your server if enough clients run sorted queries
> simultaneously.
> > You probably should back on work_mem at least an order of magnitude.
> >
>
> What's the correct way to configure this?
>
> * We have one client which needs to run really big
> transactions (therefore needs the work memory).
>
> * We also have about 200 clients which run always very small,
> short queries.
>
> Richard
>
Set the default value at postgresql.conf much lower, probably 4MB.
And just before running any big transaction raise it for
the current session only issuing a:
set work_mem = '256MB';
Regards,
Fernando.
From | Date | Subject | |
---|---|---|---|
Next Message | marcin mank | 2009-11-20 21:38:14 | Re: Postgres query completion status? |
Previous Message | Richard Neill | 2009-11-20 21:12:15 | Re: Postgres query completion status? |