From: | Bruce Momjian <bruce(at)momjian(dot)us> |
---|---|
To: | Stuart Ford <stuart(dot)ford(at)glide(dot)uk(dot)com> |
Cc: | "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: pg_largeobject.sql script not run after upgrade |
Date: | 2013-06-24 12:51:46 |
Message-ID: | 20130624125146.GC19590@momjian.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | 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(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://enterprisedb.com
+ It's impossible for everything to be true. +
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 2013-06-24 13:00:17 | Re: pg_largeobject.sql script not run after upgrade |
Previous Message | boraldomaster | 2013-06-24 12:42:27 | Re: Index scan and bitmap index scan - hard to understand how planner chooses |