| From: | Scott Marlowe <scott(dot)marlowe(at)gmail(dot)com> |
|---|---|
| To: | Greg Smith <greg(at)2ndquadrant(dot)com> |
| Cc: | pgsql-performance(at)postgresql(dot)org |
| Subject: | Re: settings input for upgrade |
| Date: | 2011-08-22 01:26:18 |
| Message-ID: | CAOR=d=3BQv_MM58kn8aYdrVD8TBoQR=4=gqMVFPH4xUocn5Uzw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
On Sun, Aug 21, 2011 at 1:20 PM, Greg Smith <greg(at)2ndquadrant(dot)com> wrote:
> deadlock_timeout = 3s
>
> You probably don't want to increase this. When you reach the point where
> you want to find slow lock issues by turning on log_lock_waits, you're just
> going to put it right back to the default again--or lower it.
All of these random changes brings up the REAL subject, that changes
should be made by measuring performance before and after each change
set and justifying each change. Just randomly throwing what seem like
good changes at the database is a surefire recipe for disaster.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Midge Brown | 2011-08-22 16:34:14 | Re: settings input for upgrade |
| Previous Message | Greg Smith | 2011-08-21 19:20:09 | Re: settings input for upgrade |