| From: | Scott Marlowe <scott(dot)marlowe(at)gmail(dot)com> |
|---|---|
| To: | Rodrigo Barboza <rodrigombufrj(at)gmail(dot)com> |
| Cc: | Jeff Janes <jeff(dot)janes(at)gmail(dot)com>, pgsql-performance <pgsql-performance(at)postgresql(dot)org> |
| Subject: | Re: Segment best size |
| Date: | 2013-04-14 05:20:56 |
| Message-ID: | CAOR=d=2a9jOV+jwyZoN+roh7gRhpK0SpkT8mxvAgeozc-VpCPA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
On Sat, Apr 13, 2013 at 9:01 PM, Rodrigo Barboza
<rodrigombufrj(at)gmail(dot)com> wrote:
> Would it help if I changed the checkpoint_completion_target to something close to 0.7 (mine is the default 0.5) or raise the checkpoint_segments (it is 32 now)?
That depends. What are your access patterns like? Do you have 1 or 2
writers, a dozen, a hundred? If you've got hundreds of active writers
then look at pooling an also commit_siblings and commit_delay.
--
To understand recursion, one must first understand recursion.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Rikard Pavelic | 2013-04-14 10:34:14 | Re: limit is sometimes not pushed in view with order |
| Previous Message | Rodrigo Barboza | 2013-04-14 03:01:13 | Re: Segment best size |