Re: Minor revision downgrade (9.2.11 -> 9.2.10)

From: Fabio Ugo Venchiarutti <fabio(at)vuole(dot)me>
To: Melvin Davidson <melvin6925(at)gmail(dot)com>, Bruce Momjian <bruce(at)momjian(dot)us>
Cc: "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org>, Russel Clarke <russell(dot)c(at)geoop(dot)com>, Brendan Cervin <brendan(dot)c(at)geoop(dot)com>
Subject: Re: Minor revision downgrade (9.2.11 -> 9.2.10)
Date: 2015-06-02 21:30:16
Message-ID: 556E2068.7070007@vuole.me
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Hi

Perfectly legitimate question.

The migration was just physical storage relocation, so the entirety of
the root file system, configuration and data was simply moved between
physical boxes.

As it turns out, the fault was at both ends in different stages: during
the first wave of outages they had bad CPU throttling settings on the
machine hardware.

That didn't improve performance by much tho: the real culprit was some
months-old package manager mishap reverting transparent huge pages to
"always" in the kernel (it was set and protected from change after a
previous troubleshooting hell).

For some reason it didn't bite us until we moved to this new machine.
And yes, there has been a reboot after the reversal. Perhaps we just got
lucky with memory allocation patterns up to that point

Thank you everyone.

Best regards

Fabio

On 03/06/15 01:20, Melvin Davidson wrote:
> I hate to ask the obvious, but have you made sure you copied over the
> postgresql.conf and pg_hba.conf to make it identical?
>
> On Tue, Jun 2, 2015 at 7:39 AM, Bruce Momjian <bruce(at)momjian(dot)us
> <mailto:bruce(at)momjian(dot)us>> wrote:
>
> On Tue, Jun 2, 2015 at 04:40:15PM +1200, Fabio Ugo Venchiarutti wrote:
> > We're fairly confident that it's an issue with the hardware but we
> > have political reasons to downgrade PG to 9.2.10 to show the hosting
> > supplier that it's their fault.
> >
> >
> > The release notes for 9.2.11 mention no data structure changes (in
> > line with the usual PG versioning policy). Is it just as safe to
> > downgrade too? We tested it on a couple non-critical boxes to no ill
> > effect whatsoever, but we'd like a second opinion before we do it on
> > the live installation too.
>
> I have rarely seen this question asked. I think minor-release
> downgrading is fine in this case.
>
> --
> Bruce Momjian <bruce(at)momjian(dot)us <mailto:bruce(at)momjian(dot)us>>
> http://momjian.us
> EnterpriseDB http://enterprisedb.com
>
> + Everyone has their own god. +
>
>
> --
> Sent via pgsql-general mailing list (pgsql-general(at)postgresql(dot)org
> <mailto:pgsql-general(at)postgresql(dot)org>)
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/pgsql-general
>
>
>
>
> --
> *Melvin Davidson*
> I reserve the right to fantasize. Whether or not you
> wish to share my fantasy is entirely up to you.

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Adrian Klaver 2015-06-02 22:00:16 Re: pl/python composite type array as input parameter
Previous Message Adrian Klaver 2015-06-02 21:26:13 Re: postgres db permissions