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

Re: BUG #2386: pg_restore doesn't restore large objects

From: Andreas Pflug <pgadmin(at)pse-consulting(dot)de>
To: Dave Page <dpage(at)vale-housing(dot)co(dot)uk>
Cc: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>, Patrick Headley <linxconsulting(at)comcast(dot)net>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-bugs(at)postgresql(dot)org
Subject: Re: BUG #2386: pg_restore doesn't restore large objects
Date: 2006-04-14 09:51:44
Message-ID: 443F70B0.6000105@pse-consulting.de (view raw or flat)
Thread:
Lists: pgsql-bugs
Dave Page wrote:
> pgAdmin just uses pg_dump/pg_restore to handle the heavy lifting.
> 
>>> When I try to restore the backup using PGAdmin III, the log 
>>> window begins to fill up. Near the end, when it should say it's 
>>> restoring the BLOBS an error message appears stating the BLOBS
>>> couldn't be restored.

This is the original output from pg_restore. pgAdmin will also log the
precise parameters used to restore in the first log line, it might help
to see those.

Regards,
Andreas

In response to

Responses

pgsql-bugs by date

Next:From: Pter SzabDate: 2006-04-14 16:04:43
Subject: BUG #2397: 1 = SELECT ASCII(CHR(257))
Previous:From: MartinDate: 2006-04-14 06:47:45
Subject: BUG #2396: SELECT to_number('6500', '999,999.99') != 650

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