Re: [GENERAL] large object does not exist after pg_migrator - Mailing list pgsql-hackers

From Jamie Fox
Subject Re: [GENERAL] large object does not exist after pg_migrator
Date
Msg-id de22a6520907151422h525abc48qce68618592754aad@mail.gmail.com
Whole thread Raw
In response to Re: [GENERAL] large object does not exist after pg_migrator  (Alvaro Herrera <alvherre@commandprompt.com>)
List pgsql-hackers
Worked great, vacuumlo finished, a vacuum -full finished amazingly quickly, very exciting.  We're pointing qa apps at it now for testing. 

For some reason though, that index has to be rebuilt after running pg_migrator.

I'll be testing on our 100GB+ prod copy shortly and will let you know if you want.

Thanks,

Jamie


On Wed, Jul 15, 2009 at 9:28 AM, Alvaro Herrera <alvherre@commandprompt.com> wrote:
Jamie Fox wrote:

> Hi -
> REINDEX INDEX pg_largeobject_loid_pn_index;
>
> This seems to have fixed the problem, lo_open of lob data is working again -
> now to see how vacuumlo likes it.

So did it work?

--
Alvaro Herrera                                http://www.CommandPrompt.com/
The PostgreSQL Company - Command Prompt, Inc.

pgsql-hackers by date:

Previous
From: Heikki Linnakangas
Date:
Subject: Re: Synch Rep for CommitFest 2009-07
Next
From: Fernando Ike de Oliveira
Date:
Subject: Re: [PATCH] Psql List Languages