Re: [PERFORM] settings input for upgrade

2011-08-22 Thread Greg Smith
On 08/22/2011 12:48 PM, Midge Brown wrote: I was pushed to put the new version into production over the weekend, which at least may provide me with some accurate feedback, and so will see what happens for a bit before addressing the disk/drive layout. The good news is that deploying onto the s

Re: [PERFORM] settings input for upgrade

2011-08-22 Thread Midge Brown
t may provide me with some accurate feedback, and so will see what happens for a bit before addressing the disk/drive layout. -Midge - Original Message - From: Greg Smith To: pgsql-performance@postgresql.org Sent: Sunday, August 21, 2011 12:20 PM Subject: Re: [PERFORM] settings

Re: [PERFORM] settings input for upgrade

2011-08-22 Thread Midge Brown
Thank you. I'll set work_mem back to 16MB and see what happens from there. -Midge - Original Message - From: Scott Marlowe To: Midge Brown Cc: pgsql-performance@postgresql.org Sent: Saturday, August 20, 2011 9:01 PM Subject: Re: [PERFORM] settings input for upgrade

Re: [PERFORM] settings input for upgrade

2011-08-21 Thread Scott Marlowe
On Sun, Aug 21, 2011 at 1:20 PM, Greg Smith 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. A

Re: [PERFORM] settings input for upgrade

2011-08-21 Thread Greg Smith
On 08/18/2011 05:55 PM, Midge Brown wrote: DB1 is 10GB and consists of multiple tables that I've spread out so that the 3 most used have their data and indexes on 6 separate RAID1 drives, the 3 next busiest have data & index on 3 drives, and the remaining tables and indexes are on the RAID10 dr

Re: [PERFORM] settings input for upgrade

2011-08-21 Thread Robert Klemme
On Sat, Aug 20, 2011 at 8:33 PM, Midge Brown wrote: > Robert, > > I was largely looking for input on whether I may have inadvertently shot > myself in the foot with some of the choices I made when setting up > postgresql 9.0, which is on different hardware than was the 7.4 setup. OK, I though the

Re: [PERFORM] settings input for upgrade

2011-08-20 Thread Midge Brown
Thank you! - Original Message - From: Scott Marlowe To: Midge Brown Cc: pgsql-performance@postgresql.org Sent: Saturday, August 20, 2011 9:01 PM Subject: Re: [PERFORM] settings input for upgrade On Thu, Aug 18, 2011 at 3:55 PM, Midge Brown wrote: > Here are

Re: [PERFORM] settings input for upgrade

2011-08-20 Thread Scott Marlowe
On Thu, Aug 18, 2011 at 3:55 PM, Midge Brown wrote: > Here are the changes I made to postgres.conf. The only differences between > the conf file for DB1 and those for DB2 & 3 are the port and > effective_cache_size (which I made slightly smaller -- 8 GB instead of 10 -- > for the 2 write-heavy DBs

Re: [PERFORM] settings input for upgrade

2011-08-20 Thread Midge Brown
:38 AM Subject: Re: [PERFORM] settings input for upgrade On Thu, Aug 18, 2011 at 11:55 PM, Midge Brown wrote: > I'm in the process of upgrading from postgres 7.4.8 to 9.0.4 and wanted to > run my decisions past some folks who can give me some input on whether my > decisions

Re: [PERFORM] settings input for upgrade

2011-08-20 Thread Robert Klemme
On Thu, Aug 18, 2011 at 11:55 PM, Midge Brown wrote: > I'm in the process of upgrading from postgres 7.4.8 to 9.0.4 and wanted to > run my decisions past some folks who can give me some input on whether my > decisions make sense or not. I am not sure what decisions you actually refer to here: in

[PERFORM] settings input for upgrade

2011-08-18 Thread Midge Brown
I'm in the process of upgrading from postgres 7.4.8 to 9.0.4 and wanted to run my decisions past some folks who can give me some input on whether my decisions make sense or not. It's basically a LAPP configuration and on a busy day we probably get in the neighborhood of a million hits. Serve