| From: | Dennis Bjorklund <db(at)zigo(dot)dhs(dot)org> |
|---|---|
| To: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
| Cc: | Vivek Khera <khera(at)kcilink(dot)com>, <pgsql-performance(at)postgresql(dot)org> |
| Subject: | Re: restore time: sort_mem vs. checkpoing_segments |
| Date: | 2003-09-24 05:24:26 |
| Message-ID: | Pine.LNX.4.44.0309240721430.352-100000@zigo.dhs.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
On Tue, 23 Sep 2003, Bruce Momjian wrote:
> With the new warning about too-frequent checkpoints, people have actual
> feedback to encourage them to increase checkpoint_segments. One issue
> is that it is likely to recommend increasing checkpoint_segments during
> restore, even if there is no value to it being large during normal
> server operation. Should that be decumented?
One could have a variable that turns off that warning, and have pg_dump
insert a statement to turn it off. That is, if one never want these
warnings from a restore (from a new dump).
In any case, documentation is good and still needed.
--
/Dennis
| From | Date | Subject | |
|---|---|---|---|
| Next Message | peter | 2003-09-24 05:48:15 | Performance issue |
| Previous Message | Dennis Bjorklund | 2003-09-24 05:20:44 | Re: LIKE query running slow |