| From: | Scott Marlowe <scott(dot)marlowe(at)gmail(dot)com> |
|---|---|
| To: | Ben Chobot <bench(at)silentmedia(dot)com> |
| Cc: | Kyriacos Kyriacou <kyriacosk(at)prime-tel(dot)com>, PostgreSQL - Performance <pgsql-performance(at)postgresql(dot)org> |
| Subject: | Re: MVCC performance issue |
| Date: | 2010-11-12 17:48:39 |
| Message-ID: | AANLkTinjw0ifzmPi=utCYda=c1gCoX3Rm2reNT=kPy-+@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
On Fri, Nov 12, 2010 at 9:19 AM, Ben Chobot <bench(at)silentmedia(dot)com> wrote:
> On Nov 12, 2010, at 8:14 AM, Kyriacos Kyriacou wrote:
>
> We are still using PostgreSQL 8.2.4. We are running a 24x7 system and
> database size is over 200Gb so upgrade is not an easy decision!
>
> This is why we have slony, so you can slowly upgrade your 200Gb while you're
> live and then only suffer a minute or so of downtime while you switchover.
> Even if you only install slony for the point of the upgrade and then
> uninstall it after you're done, that seems well worth it to me rather than
> running on 8.2.4 for a while.
> Note there were some changes between 8.2 and 8.3 in regards to casting that
> might make you revisit your application.
I work in a slony shop and we used slony to upgrade from 8.2 to 8.3
and it was a breeze. Course we practiced on some test machines first,
but it went really smoothly. Our total downtime, due to necessary
testing before going live again, was less than 20 mintues.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Scott Carey | 2010-11-12 18:13:23 | Re: MVCC performance issue |
| Previous Message | Scott Marlowe | 2010-11-12 17:39:55 | Re: MVCC performance issue |