| From: | Rodrigo Barboza <rodrigombufrj(at)gmail(dot)com> |
|---|---|
| To: | Jeff Janes <jeff(dot)janes(at)gmail(dot)com> |
| Cc: | pgsql-performance <pgsql-performance(at)postgresql(dot)org> |
| Subject: | Re: Segment best size |
| Date: | 2013-04-13 17:29:13 |
| Message-ID: | CANs8QJYuQbF=qQ9JqBJ8YcO2SptR5LL3RK0Nv6GioriakB+8-Q@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
On Fri, Apr 12, 2013 at 10:20 PM, Jeff Janes <jeff(dot)janes(at)gmail(dot)com> wrote:
> On Friday, April 12, 2013, Rodrigo Barboza wrote:
>
>> Hi guys.
>> I compiled my postrges server (9.1.4) with default segment size (16MB).
>> Should it be enough? Should I increase this size in compilation?
>>
>
> To recommend that you deviate from the defaults, we would have to know
> something about your server, or how you intend to use it. But you haven't
> told us any of those things. Is there something about your intended use of
> the server that made you wonder about this setting in particular?
>
> Anyway, wal seg size is one of the last things I would worry about
> changing. Also, I suspect non-default settings of that parameter get
> almost zero testing (either alpha, beta, or in the field), and so would
> consider it mildly dangerous to deploy to production.
>
> Cheers,
>
> Jeff
>
I was receiving warning messages of pgstat timeout.
I started looking for the solution for this problem and this doubt came out.
But it doesn't seem to be the problem.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Rikard Pavelic | 2013-04-13 18:08:16 | Re: limit is sometimes not pushed in view with order |
| Previous Message | Steve Singer | 2013-04-13 16:14:10 | Re: slow bitmap heap scans on pg 9.2 |