pg_dump/pg_restore - Mailing list pgsql-bugs

From Colin Stearman
Subject pg_dump/pg_restore
Date
Msg-id 001e01c29378$23a13040$3301a8c0@Colin2000
Whole thread Raw
List 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 w=
hen 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=20

This is version 7.2.3 and the pg_dump used -c -C -o -Fc -Z1 -b switches,  p=
g_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

pgsql-bugs by date:

Previous
From: Luis Mota
Date:
Subject: Re: Bug #822: Condition on rule is not respected.
Next
From: Adam Buraczewski
Date:
Subject: PostgreSQL 7.3rc1: initdb fais with '-W' switch given in the command line.