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 16:18:07 |
Message-ID: | 20130624161807.GA4715@momjian.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Mon, Jun 24, 2013 at 03:25:44PM +0000, Stuart Ford wrote:
> On 24/06/2013 14:00, "Bruce Momjian" <bruce(at)momjian(dot)us> wrote:
>
>
> >
> >Looking further, here is the command that is executed:
> >
> > SELECT pg_catalog.lo_create(t.loid)
> > FROM (SELECT DISTINCT loid FROM pg_catalog.pg_largeobject) AS t;
> >
> >If you have created _new_ large objects since the upgrde, the script
> >might throw an error, as there is already metadata for those large
> >objects. You might need to delete the rows in pg_largeobject_metadata
> >before running the script; this will reset all the large object
> >permissions to default.
>
> There doesn't appear to be, if this command, which returns 0, is correct:
>
> select count(*) from pg_catalog.pg_largeobject_metadata ;
>
> So it's OK to go ahead and run at any time?
Yep. If it fails for some reason, just delete the contents of
pg_largeobject_metadata and run it again.
--
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 | Dmitriy Igrishin | 2013-06-24 16:22:53 | Re: Re: [HACKERS] Frontend/backend protocol improvements proposal (request). |
Previous Message | Joshua D. Drake | 2013-06-24 15:33:39 | Re: Strict mode in postgresql?? |