From: Tom Lane <tgl@sss.pgh.pa.us>
To: Adi Alurkar <adi@sf.net>
Cc: pgsql-performance@postgresql.org
Subject: Re: Dump/Restore performance improvement
Date: Sun, 05 Sep 2004 13:07:43 -0400
Message-ID: <29496.1094404063@sss.pgh.pa.us> (raw)
In-Reply-To: <18A61C72-FEF1-11D8-8BA3-000A95C4BD7A@sf.net>
References: <18A61C72-FEF1-11D8-8BA3-000A95C4BD7A@sf.net>
Adi Alurkar <adi@sf.net> writes:
> 1) Add a new config paramter e.g work_maintanence_max_mem this will
> the max memory postgresql *can* claim if need be.
> 2) During the dump phase of the DB postgresql estimates the
> "work_maintenance_mem" that would be required to create the index in
> memory(if possible) and add's a
> SET work_maintenance_mem="the value calculated" (IF this value is less
> than work_maintanence_max_mem. )
This seems fairly pointless to me. How is this different from just
setting maintenance_work_mem as large as you can stand before importing
the dump?
Making any decisions at dump time seems wrong to me in the first place;
pg_dump should not be expected to know what conditions the restore will
be run under. I'm not sure that's what you're proposing, but I don't
see what the point is in practice. It's already the case that
maintenance_work_mem is treated as the maximum memory you can use,
rather than what you will use even if you don't need it all.
regards, tom lane
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: tgl@sss.pgh.pa.us, adi@sf.net
Subject: Re: Dump/Restore performance improvement
In-Reply-To: <29496.1094404063@sss.pgh.pa.us>
* 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