From: | Robert Klemme <shortcutter(at)googlemail(dot)com> |
---|---|
To: | Midge Brown <midgems(at)sbcglobal(dot)net> |
Cc: | pgsql-performance(at)postgresql(dot)org |
Subject: | Re: settings input for upgrade |
Date: | 2011-08-20 09:38:58 |
Message-ID: | CAM9pMnOCvsAj4rwYene8vekgtZuEpafdPphTGOcMFHqG-_oEnw@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-performance |
On Thu, Aug 18, 2011 at 11:55 PM, Midge Brown <midgems(at)sbcglobal(dot)net> 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 your
posting I can only see description of the current setup but no
decisions for the upgrade (i.e. changed parameters, other physical
layout etc.).
> The others are very write-heavy, started as one table within the original
> DB, and were split out on an odd/even id # in an effort to get better
> performance:
Did it pay off? I mean you planned to increase performance and did
this actually happen? Apart from reserving IO bandwidth (which you
achieved by placing data on different disks) you basically only added
reserved memory for each instance by separating them. Or are there
any other effects achieved by separating (like reduced lock contention
on some globally shared resource, distribution of CPU for logging)?
Kind regards
robert
--
remember.guy do |as, often| as.you_can - without end
http://blog.rubybestpractices.com/
From | Date | Subject | |
---|---|---|---|
Next Message | Midge Brown | 2011-08-20 18:33:45 | Re: settings input for upgrade |
Previous Message | hyelluas | 2011-08-19 21:14:53 | Re: tunning strategy needed |