Skip site navigation (1) Skip section navigation (2)

Re: [GENERAL] large object does not exist afterpg_migrator

From: Alvaro Herrera <alvherre(at)commandprompt(dot)com>
To: Bruce Momjian <bruce(at)momjian(dot)us>
Cc: Jamie Fox <jfox(at)directcommerce(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgreSQL(dot)org>
Subject: Re: [GENERAL] large object does not exist afterpg_migrator
Date: 2009-07-13 22:35:45
Message-ID: 20090713223545.GP4930@alvh.no-ip.org (view raw or flat)
Thread:
Lists: pgsql-generalpgsql-hackers 
Bruce Momjian wrote:
> Jamie Fox wrote:

> > I can also see that the pg_largeobject table is different, in the pg_restore
> > version the Rows (estimated) is 316286 and Rows (counted) is the same, in
> > the pg_migrator version the Rows (counted) is only 180507.

> Wow, I didn't test large objects specifically, and I am confused why
> there would be a count discrepancy. I will need to do some research
> unless someone else can guess about the cause.

Maybe pg_largeobject is not getting frozen?

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

In response to

Responses

pgsql-hackers by date

Next:From: Bruce MomjianDate: 2009-07-13 22:38:13
Subject: Re: [GENERAL] large object does not exist after pg_migrator
Previous:From: Bruce MomjianDate: 2009-07-13 22:30:17
Subject: Re: pg_migrator not setting values of sequences?

pgsql-general by date

Next:From: Bruce MomjianDate: 2009-07-13 22:38:13
Subject: Re: [GENERAL] large object does not exist after pg_migrator
Previous:From: Bruce MomjianDate: 2009-07-13 22:30:17
Subject: Re: pg_migrator not setting values of sequences?

Privacy Policy | About PostgreSQL
Copyright © 1996-2013 The PostgreSQL Global Development Group