Re: [GENERAL] large object does not exist after pg_migrator

From: Alvaro Herrera <alvherre(at)commandprompt(dot)com>
To: Jamie Fox <jfox(at)directcommerce(dot)com>
Cc: Bruce Momjian <bruce(at)momjian(dot)us>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: [GENERAL] large object does not exist after pg_migrator
Date: 2009-07-14 19:03:04
Message-ID: 20090714190304.GL4799@alvh.no-ip.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general pgsql-hackers

Jamie Fox wrote:

> Here's what I have found that got broken during pg_migrate: In two side by
> side databases (an 8.3.7 copy and 8.4.0 migrated with pg_migrator) the
> pg_largeobject table has the same number of rows. However, in the 8.4
> database any select for an loid in pg_largeobject returns zero rows. If I
> select all loids to a file, and compare to select all loids from 8.3.7
> they're the same. When I select != an loid it seems to exclude the one and
> return the rest, but all other comparisons <, > or = return zero rows. Or
> I'm completely batty. Dereferencing via lo_open of blob_data (an oid) in
> other tables fails in the 8.4 database with 'large object xxxxid does not
> exist'.

Oh, so maybe it's pg_largeobject's index that's borked ... Did you try
reindexing it?

How are we transferring pg_largeobject, and are we transferring its
index too?

--
Alvaro Herrera http://www.CommandPrompt.com/
PostgreSQL Replication, Consulting, Custom Development, 24x7 support

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Kevin Kempter 2009-07-14 19:03:27 Re: [Q] single image Table across multiple PG servers
Previous Message Jamie Fox 2009-07-14 18:59:39 Re: [GENERAL] large object does not exist after pg_migrator

Browse pgsql-hackers by date

  From Date Subject
Next Message Stefan Moeding 2009-07-14 19:04:39 Re: Sampling profiler updated
Previous Message Alvaro Herrera 2009-07-14 19:00:14 Re: WIP: Deferrable unique constraints