Re: pg_largeobject.sql script not run after upgrade - Mailing list pgsql-general

From Bruce Momjian
Subject Re: pg_largeobject.sql script not run after upgrade
Date
Msg-id 20130624125146.GC19590@momjian.us
Whole thread Raw
In response to pg_largeobject.sql script not run after upgrade  (Stuart Ford <stuart.ford@glide.uk.com>)
Responses Re: pg_largeobject.sql script not run after upgrade  (Bruce Momjian <bruce@momjian.us>)
List pgsql-general
On Mon, Jun 24, 2013 at 11:13:08AM +0000, Stuart Ford wrote:
> Dear community
>
> Last week we upgraded our database from 8.4 to 9.1. The upgrade seemed to
> go fine and the database seems to have been working fine ever since
> (around a week now).
>
> However, today I noticed the output from the pg_upgrade command contained
> the following:
>
> | Your installation contains large objects.
> | The new database has an additional large object
> | permission table so default permissions must be
> | defined for all large objects.  The file:
> |     /tmp/pg_largeobject.sql
> | when executed by psql by the database super-user
> | will define the default permissions.
>
> I missed this at the time, my fault, it was at the end of a stressful
> migration evening.
>
> Is it safe to run this script now, a week in to using the upgraded
> database? Can this be done while the database is live?

Sure, you can run it anytime.  Until you run it your large object
permissions might not be accurate.

--
  Bruce Momjian  <bruce@momjian.us>        http://momjian.us
  EnterpriseDB                             http://enterprisedb.com

  + It's impossible for everything to be true. +


pgsql-general by date:

Previous
From: boraldomaster
Date:
Subject: Re: Index scan and bitmap index scan - hard to understand how planner chooses
Next
From: Bruce Momjian
Date:
Subject: Re: pg_largeobject.sql script not run after upgrade