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

pg_dump/pg_restore

From: "Colin Stearman" <cstearman(at)infofind(dot)com>
To: <pgsql-bugs(at)postgresql(dot)org>
Subject: pg_dump/pg_restore
Date: 2002-11-24 16:56:35
Message-ID: 001801c293da$731e14a0$af7ba8c0@ne2.client2.attbi.com (view raw or flat)
Thread:
Lists: pgsql-bugs
Hi,

2 possible bugs in pg_dump/pg_restore related to large objects.

1. Large objects dumped, deleted then restored do not retain their original OIDs.  Big problem as we reference their OIDs in tables.
2. The pg_restore command --list indicated no Blobs in the dump file even when there are.  For example:
  .
  .
  72; 46588445 TABLE DATA table_3da6183d8bb21 nobody
  73; 46588481 TABLE DATA table_3da625d622b72 nobody
  74; 46588517 TABLE DATA table_3da625f19cc95 nobody
  75; 0 BLOBS BLOBS 

This is version 7.2.3 and the pg_dump used -c -C -o -Fc -Z1 -b switches,  pg_restore used no switches (other than -d, of course).

Thanks,
Colin
---------------------------------------------
Colin Stearman
President
Ashdown Technologies
119 E. Main St.
Milford, MA 01757 USA
Tel: +1 508-478-1234
Fax: +1 508-478-1244
www.ashdowntech.com

Responses

pgsql-bugs by date

Next:From: Adam BuraczewskiDate: 2002-11-24 17:37:09
Subject: PostgreSQL 7.3rc1: initdb fais with '-W' switch given in the command line.
Previous:From: Colin StearmanDate: 2002-11-24 05:12:49
Subject: pg_dump/pg_restore

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