| From: | Igor Neyman <ineyman(at)perceptron(dot)com> |
|---|---|
| To: | Thomas Kellerer <spam_eater(at)gmx(dot)net>, "pgsql-performance(at)postgresql(dot)org" <pgsql-performance(at)postgresql(dot)org> |
| Subject: | Re: Postgres becoming slow, only full vacuum fixes it |
| Date: | 2012-10-01 14:09:25 |
| Message-ID: | A76B25F2823E954C9E45E32FA49D70EC08EB681C@mail.corp.perceptron.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
> -----Original Message-----
> From: Thomas Kellerer [mailto:spam_eater(at)gmx(dot)net]
> Sent: Tuesday, September 25, 2012 7:24 AM
> To: pgsql-performance(at)postgresql(dot)org
> Subject: Re: Postgres becoming slow, only full vacuum fixes it
>
> Kiriakos Tsourapas, 25.09.2012 13:01:
> > Thank you,
> >
> > I will take this into consideration, since upgrading to 9 will be
> much harder I assume...
> >
>
> I think an upgrade from 8.3 to 8.4 was "harder" due to the removal of a
> lot of implicit type casts.
> 8.4 to 9.x shouldn't be that problematic after all (but will take
> longer due to the required dump/reload)
>
Actually, 8.3 to 8.4 required db dump/restore.
When upgrading from 8.4 to 9.x pg_upgrade could be used without dump/restore.
Regards,
Igor Neyman
| From | Date | Subject | |
|---|---|---|---|
| Next Message | pg noob | 2012-10-01 16:49:53 | deadlock_timeout affect on performance |
| Previous Message | henk de wit | 2012-09-29 12:40:35 | Re: Spurious failure to obtain row lock possible in PG 9.1? |