pg.ddx.io pgsql-admin@postgresql.org mailing list archive
help / color / mirror / Atom feedSet maintenance work mem for pg_restore
5+ messages / 4 participants
[nested] [flat]
* Set maintenance work mem for pg_restore
@ 2007-12-18 20:30 Deron <fecastle@gmail.com>
0 siblings, 3 replies; 5+ messages in thread
From: Deron @ 2007-12-18 20:30 UTC (permalink / raw)
To: pgsql-admin
I see a lot of suggestions to increase maintenance work mem if running
pg_restore. This is to help with the index creation and initial sort from
what I understand. A few tests I ran does show this helps.
Does anyone know if there is a way to only "temporarily" set this setting?
I have some DBs that are bloated and I have a script to run off hours (I
don't like working late). This uses pg_dump and pg_restore to recover the
disk space. I found that this is usually faster than 'vacuum full', and is
useful in some cases.
I know I can set this for my current session dynamically "set
maintenance_work_mem = xxxxx", but it seems that the only way I can do this
for pg_restore is to update the configuration, reload and then change it
back when the script completes and reload again.
Thanks
Deron
^ permalink raw reply [nested|flat] 5+ messages in thread
* Re: Set maintenance work mem for pg_restore
@ 2007-12-18 20:49 Alvaro Herrera <alvherre@commandprompt.com>
parent: Deron <fecastle@gmail.com>
2 siblings, 1 reply; 5+ messages in thread
From: Alvaro Herrera @ 2007-12-18 20:49 UTC (permalink / raw)
To: Deron <fecastle@gmail.com>; +Cc: pgsql-admin
Deron escribió:
> I see a lot of suggestions to increase maintenance work mem if running
> pg_restore. This is to help with the index creation and initial sort from
> what I understand. A few tests I ran does show this helps.
> Does anyone know if there is a way to only "temporarily" set this setting?
> I have some DBs that are bloated and I have a script to run off hours (I
> don't like working late). This uses pg_dump and pg_restore to recover the
> disk space. I found that this is usually faster than 'vacuum full', and is
> useful in some cases.
You can specify it via PGOPTIONS:
$ PGOPTIONS='-c maintenance_work_mem=1GB' psql
Welcome to psql 8.2.5, the PostgreSQL interactive terminal.
Type: \copyright for distribution terms
\h for help with SQL commands
\? for help with psql commands
\g or terminate with semicolon to execute query
\q to quit
alvherre=# show maintenance_work_mem ;
maintenance_work_mem
----------------------
1GB
(1 row)
alvherre=# \q
$ psql
Welcome to psql 8.2.5, the PostgreSQL interactive terminal.
Type: \copyright for distribution terms
\h for help with SQL commands
\? for help with psql commands
\g or terminate with semicolon to execute query
\q to quit
alvherre=# show maintenance_work_mem ;
maintenance_work_mem
----------------------
16MB
(1 row)
--
Alvaro Herrera http://www.CommandPrompt.com/
PostgreSQL Replication, Consulting, Custom Development, 24x7 support
^ permalink raw reply [nested|flat] 5+ messages in thread
* Re: Set maintenance work mem for pg_restore
@ 2007-12-18 20:54 Scott Marlowe <scott.marlowe@gmail.com>
parent: Deron <fecastle@gmail.com>
2 siblings, 0 replies; 5+ messages in thread
From: Scott Marlowe @ 2007-12-18 20:54 UTC (permalink / raw)
To: Deron <fecastle@gmail.com>; +Cc: pgsql-admin
On Dec 18, 2007 2:30 PM, Deron <fecastle@gmail.com> wrote:
> I see a lot of suggestions to increase maintenance work mem if running
> pg_restore. This is to help with the index creation and initial sort from
> what I understand. A few tests I ran does show this helps.
> Does anyone know if there is a way to only "temporarily" set this setting?
> I have some DBs that are bloated and I have a script to run off hours (I
> don't like working late). This uses pg_dump and pg_restore to recover the
> disk space. I found that this is usually faster than 'vacuum full', and is
> useful in some cases.
>
> I know I can set this for my current session dynamically "set
> maintenance_work_mem = xxxxx", but it seems that the only way I can do this
> for pg_restore is to update the configuration, reload and then change it
> back when the script completes and reload again.
If you use psql to restore, you can just add the set
maintenance_work_mem = xxx at the top of the file.
Also you can do it by creating a "special" superuser and altering that
user to inherit this new setting:
create user bubba superuser;
alter user bubba set maintenance_work_mem TO 512000;
then just connect as that user to run your restores or what not. You
can also set it for a non-super user, or a database as well.
^ permalink raw reply [nested|flat] 5+ messages in thread
* Re: Set maintenance work mem for pg_restore
@ 2007-12-18 21:21 Tom Lane <tgl@sss.pgh.pa.us>
parent: Deron <fecastle@gmail.com>
2 siblings, 0 replies; 5+ messages in thread
From: Tom Lane @ 2007-12-18 21:21 UTC (permalink / raw)
To: Deron <fecastle@gmail.com>; +Cc: pgsql-admin
Deron <fecastle@gmail.com> writes:
> Does anyone know if there is a way to only "temporarily" set this setting?
Aside from the specific answers already given, the general answer is to
read
http://www.postgresql.org/docs/8.2/static/config-setting.html
which enumerates all (most?) of the many ways you can set configuration
parameters.
regards, tom lane
^ permalink raw reply [nested|flat] 5+ messages in thread
* Re: Set maintenance work mem for pg_restore
@ 2007-12-18 22:40 Deron <fecastle@gmail.com>
parent: Alvaro Herrera <alvherre@commandprompt.com>
0 siblings, 0 replies; 5+ messages in thread
From: Deron @ 2007-12-18 22:40 UTC (permalink / raw)
To: pgsql-admin
Thanks for this and the other suggestions. This is exactly what I was
looking for.
Deron
On 12/18/07, Alvaro Herrera <alvherre@commandprompt.com> wrote:
>
> Deron escribió:
> > I see a lot of suggestions to increase maintenance work mem if running
> > pg_restore. This is to help with the index creation and initial sort
> from
> > what I understand. A few tests I ran does show this helps.
> > Does anyone know if there is a way to only "temporarily" set this
> setting?
> > I have some DBs that are bloated and I have a script to run off hours (I
> > don't like working late). This uses pg_dump and pg_restore to recover
> the
> > disk space. I found that this is usually faster than 'vacuum full', and
> is
> > useful in some cases.
>
> You can specify it via PGOPTIONS:
>
> $ PGOPTIONS='-c maintenance_work_mem=1GB' psql
> Welcome to psql 8.2.5, the PostgreSQL interactive terminal.
>
> Type: \copyright for distribution terms
> \h for help with SQL commands
> \? for help with psql commands
> \g or terminate with semicolon to execute query
> \q to quit
>
> alvherre=# show maintenance_work_mem ;
> maintenance_work_mem
> ----------------------
> 1GB
> (1 row)
>
> alvherre=# \q
>
> $ psql
> Welcome to psql 8.2.5, the PostgreSQL interactive terminal.
>
> Type: \copyright for distribution terms
> \h for help with SQL commands
> \? for help with psql commands
> \g or terminate with semicolon to execute query
> \q to quit
>
> alvherre=# show maintenance_work_mem ;
> maintenance_work_mem
> ----------------------
> 16MB
> (1 row)
>
>
>
> --
> Alvaro Herrera
> http://www.CommandPrompt.com/
> PostgreSQL Replication, Consulting, Custom Development, 24x7 support
>
^ permalink raw reply [nested|flat] 5+ messages in thread
end of thread, other threads:[~2007-12-18 22:40 UTC | newest]
Thread overview: 5+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2007-12-18 20:30 Set maintenance work mem for pg_restore Deron <fecastle@gmail.com>
2007-12-18 20:49 ` Alvaro Herrera <alvherre@commandprompt.com>
2007-12-18 22:40 ` Deron <fecastle@gmail.com>
2007-12-18 20:54 ` Scott Marlowe <scott.marlowe@gmail.com>
2007-12-18 21:21 ` Tom Lane <tgl@sss.pgh.pa.us>
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