| From: | "Scott Marlowe" <scott(dot)marlowe(at)gmail(dot)com> |
|---|---|
| To: | "Martijn van Oosterhout" <kleptog(at)svana(dot)org>, Clodoaldo <clodoaldo(dot)pinto(dot)neto(at)gmail(dot)com>, "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>, "Scott Marlowe" <scott(dot)marlowe(at)gmail(dot)com>, "PostgreSQL - General ML" <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: ATTN: Clodaldo was Performance problem. Could it be related to 8.3-beta4? |
| Date: | 2008-01-20 13:32:39 |
| Message-ID: | dcc563d10801200532o4bc1d075w1dff8d68c9e04ffd@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Jan 20, 2008 6:44 AM, Martijn van Oosterhout <kleptog(at)svana(dot)org> wrote:
> On Sun, Jan 20, 2008 at 09:29:16AM -0200, Clodoaldo wrote:
> > Will "enable_hashagg" be settable(*) per query or only at server start/reload?
>
> The enable_* settings are per session, so you can disable hashagg just
> before the query and reenable it just after, or disable it for just
> that process/user/database whatever you like.
>
> I think the word you're looking for is "configurable".
And don't forget
alter {user|database} xyz set enable_hashagg={on|off};
| From | Date | Subject | |
|---|---|---|---|
| Next Message | walterbyrd | 2008-01-20 14:34:46 | Re: Sun acquires MySQL |
| Previous Message | Martijn van Oosterhout | 2008-01-20 12:44:13 | Re: ATTN: Clodaldo was Performance problem. Could it be related to 8.3-beta4? |