| From: | Thomas F(dot)O'Connell <tfo(at)sitening(dot)com> |
|---|---|
| To: | "PgSQL General" <pgsql-general(at)postgresql(dot)org> |
| Subject: | checkpoint_timeout |
| Date: | 2005-03-22 23:15:28 |
| Message-ID: | 367bd835ee9894314da4bc8be54d837e@sitening.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
In the annotated conf file for 8.0, Josh Berkus notes that
checkpoint_timeout should be increased "dramatically" for large data
loads. For settings like sort_mem (now work_mem), it's been convenient
to be able to have a default setting for standard work and a
per-connection configuration option.
Instinctively, it seems like it would be nice to have something similar
for checkpoint_timeout, but is there any disadvantage to having a value
"dramatically" higher than the default for general use, considering
that checkpoint_timeout can only be set at server start?
-tfo
--
Thomas F. O'Connell
Co-Founder, Information Architect
Sitening, LLC
http://www.sitening.com/
110 30th Avenue North, Suite 6
Nashville, TN 37203-6320
615-260-0005
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Greg Stark | 2005-03-22 23:33:54 | Re: Changing constraints to deferrable |
| Previous Message | Jeff Davis | 2005-03-22 20:48:09 | Re: PHP SQL |