From: | Andres Freund <andres(at)anarazel(dot)de> |
---|---|
To: | pgsql-performance(at)postgresql(dot)org |
Cc: | Samuel Gendler <sgendler(at)ideasculptor(dot)com> |
Subject: | Re: setting configuration values inside a stored proc |
Date: | 2011-05-13 08:28:15 |
Message-ID: | 201105131028.15694.andres@anarazel.de |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-performance |
Hi,
On Friday, May 13, 2011 01:10:19 AM Samuel Gendler wrote:
> I've got a stored proc that constructs some aggregation queries as strings
> and then executes them. I'd like to be able to increase work_mem before
> running those queries. If I set a new value for work_mem within the stored
> proc prior to executing my query string, will that actually have an impact
> on the query or is work_mem basically a constant once the outer statement
> that calls the stored proc has begun? I'd just test, but it will take
> hours for me to grab a copy of production data and import into a new db
> host for testing. I've already started that process, but I'm betting I'll
> have an answer by the time it completes. It's just the difference between
> modifying the application which calls the procs (and doing a full software
> release in order to do so or else waiting a month to go in the next
> release) vs modifying the procs themselves, which requires only db a
> update.
I would suggest doing ALTER FUNCTION blub(blarg) SET work_mem = '512MB';
Andres
From | Date | Subject | |
---|---|---|---|
Next Message | tv | 2011-05-13 08:44:47 | Re: [ADMIN] since when has pg_stat_user_indexes.idx_scan been counting? |
Previous Message | Greg Smith | 2011-05-13 02:26:03 | Re: [ADMIN] since when has pg_stat_user_indexes.idx_scan been counting? |