From: John Vincent <pgsql-performance@lusis.org>
To: Scott Marlowe <smarlowe@g2switchworks.com>
Cc: PGSQL Performance <pgsql-performance@postgresql.org>
Subject: Re: Performance of pg_dump on PGSQL 8.0
Date: Wed, 14 Jun 2006 16:55:00 -0400
Message-ID: <c841561b0606141355g5b00b27ey257bbfc661dccfb@mail.gmail.com> (raw)
In-Reply-To: <1150315897.26538.33.camel@state.g2switchworks.com>
References: <44902165.7020502@lusis.org>
<1150303450.26538.9.camel@state.g2switchworks.com>
<c841561b0606141004w62d584ake46d598ccb1a4b22@mail.gmail.com>
<1150315897.26538.33.camel@state.g2switchworks.com>
On 6/14/06, Scott Marlowe <smarlowe@g2switchworks.com> wrote:
>
>
> Description of "Queries gone wild" redacted. hehe.
>
> Yeah, I've seen those kinds of queries before too. you might be able to
> limit your exposure by using alter user:
>
> alter user userwhoneedslotsofworkmem set work_mem=1000000;
Is this applicable on 8.0? We were actually LOOKING for a governor of some
sort for these queries. And something that is not explicitly stated, is
that allocated up front or is that just a ceiling?
and then only that user will have that big of a default. You could even
> make it so that only queries that need that much log in as that user,
> and all other queries log in as other folks. Just a thought. I just
> get REAL nervous seeing a production machine with a work_mem set that
> high.
Which is actually how it's configured. We have a dedicated user connecting
from Actuate. The reports developers use thier own logins when developing
new reports. Only when they get published do they convert to the Actuate
user.
--
John E. Vincent
lusis.org@gmail.com
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-performance@postgresql.org
Cc: pgsql-performance@lusis.org, smarlowe@g2switchworks.com
Subject: Re: Performance of pg_dump on PGSQL 8.0
In-Reply-To: <c841561b0606141355g5b00b27ey257bbfc661dccfb@mail.gmail.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox