From: | Jeff Janes <jeff(dot)janes(at)gmail(dot)com> |
---|---|
To: | Álvaro Nunes Lemos Melo <al_nunes(at)atua(dot)com(dot)br> |
Cc: | "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: Upgrading from 9.2 to 9.3 causes performance degradation |
Date: | 2014-03-24 18:29:38 |
Message-ID: | CAMkU=1x04XLDJ0Re3LtChUiPPRyRDozGVKBw1SQ2Th8ypPrd=Q@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Mon, Mar 24, 2014 at 7:45 AM, Álvaro Nunes Lemos Melo <
al_nunes(at)atua(dot)com(dot)br> wrote:
> ==> Venkata
> > After the migration to hardware and to the new version 9.3, any changes
> have been done in the postgresql.conf compared to the old settings ?
> No, as I wrote initially, I'd double checked and the four conf files have
> the same parameters.
>
> > Any maintenance activities (VACUUM or VACUUM FULL and ANALYZE) have been
> performed after the migration ?
> ANALYZE yes. VACUUM or VACUUM FULL no, because I ran the test on recently
> restores and unchanged databases.
>
How did you do the restore? Please VACUUM and retest. At best it will fix
the problem, and if it doesn't it will at least rule out a bunch of
possibilities for the source of the problem.
Cheers,
Jeff
From | Date | Subject | |
---|---|---|---|
Next Message | john.tiger | 2014-03-24 22:16:40 | thanks core team for jsonb |
Previous Message | Ken Barber | 2014-03-24 17:59:25 | Re: General Advice for avoiding concurrency during schema migrations |