From: Benjamin Krajmalnik <kraj@servoyant.com>
To: Kevin Grittner <Kevin.Grittner@wicourts.gov>
To: pgsql-admin <pgsql-admin@postgresql.org>
Subject: Re: Upgrading from 9.0.3 to latest
Date: Wed, 18 Jan 2012 15:32:00 -0700
Message-ID: <F4E6A2751A2823418A21D4A160B689888CA71D@fletch.stackdump.local> (raw)
In-Reply-To: <4F16F3180200002500044986@gw.wicourts.gov>
References: <F4E6A2751A2823418A21D4A160B689888CA71C@fletch.stackdump.local>
<4F16F3180200002500044986@gw.wicourts.gov>
If I have never used pg_upgrade, so I believe I do not need to do
anything, correct?
> -----Original Message-----
> From: Kevin Grittner [mailto:Kevin.Grittner@wicourts.gov]
> Sent: Wednesday, January 18, 2012 3:28 PM
> To: pgsql-admin; Benjamin Krajmalnik
> Subject: Re: [ADMIN] Upgrading from 9.0.3 to latest
>
> "Benjamin Krajmalnik" <kraj@servoyant.com> wrote:
>
> > I will be taking down all of our infrastructure to update firmware
> > on the controllers due to a bug affecting BBU (wonderful J ).
> >
> > I was thinking of taking the opportunity and upgrading pg from
> > 9.0.3 (amd64 on Freebsd 8.1) to the latest version 9.0.6.
>
> That sounds like a good idea.
>
> > In the release notes for 9.0.6, it mentions:
> >
> > fix bugs in information_schema.referential_constraints view (Tom
> > Lane)
> >
> > Is the dropping and recreation of this mandatory,
>
> If you don't do it, I don't think you're any worse off than you were
> while at version 9.0.3; you will just not have fixed the view.
>
> > can it be done at any time while the server is already being
> > pounded with data?
>
> I would tend to do it as part of the upgrade process. I don't think
> it take very long to run. If you do it while queries are running,
> you will get errors if any of them reference the information_schema
> schema, they will get runtime errors on missing objects.
>
> Probably more important is to make sure that you have considered
> this issue, and taken action if necessary:
>
> http://wiki.postgresql.org/wiki/20110408pg_upgrade_fix
>
> -Kevin
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients from your mail client; the link fills in
the headers below: reply via email
Some clients, webmail especially, drop In-Reply-To and References from
a link, and the reply then starts a new thread: use the mbox below.
To: pgsql-admin@postgresql.org
Cc: kraj@servoyant.com, Kevin.Grittner@wicourts.gov
Subject: Re: Upgrading from 9.0.3 to latest
In-Reply-To: <F4E6A2751A2823418A21D4A160B689888CA71D@fletch.stackdump.local>
References: <F4E6A2751A2823418A21D4A160B689888CA71C@fletch.stackdump.local> <4F16F3180200002500044986@gw.wicourts.gov> <F4E6A2751A2823418A21D4A160B689888CA71D@fletch.stackdump.local>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox