On Fri, Apr 20, 2001 at 11:37:13AM +0200, Peter Pilsl wrote:
> On Fri, Apr 20, 2001 at 10:27:11AM +0200, Karel Zak wrote:
> > Try:
> >
> > pg_dumplo -a -d my_db -s /my_dump/dir
> > pg_dump [with relevant options for your DB] > my.dump
> > DROP DATABASE my_db;
> > CREATE DATABASE my_db;
> > psql my_db < my.dump
> > pg_dumplo -i -d my_db -s /my_dump/dir
> >
>
> when working on an own database things works perfect. However I have a
> reproduceable problem on a different database when importing blobs
> into a single table while the old blobs still existing (no matter if
> using -r or not)
Do you have right permissions for DB and dirs with LO dumps?
> However: the problem is not happening on a new created database, so
> maybe there is a problem on my system.
Hmm.. may be, sounds curious if everythig is right on mew DB.
> I will install 7.1 on a different machine and try if I can import all
> my data before migrating to 7.1 on a production-server.
The LO dump format is same for 7.0 and 7.1. If you use pg_dumplo from
7.1 for LO data from 7.0 you probably import all without problems.
> When I want to migrate _all_ data from one 7.1 to another 7.1 : does a
> brute filecopy do it ?
Means "brute filecopy" copy backend store files? IMHO it's really brutal
way, more standard is dump out and import all back to new DB.
The pg_dump in 7.1 dumping LO too. My pg_dumplo is a crutch for old PG
versions and for export/import without spec. oid operations (like new
pg_dump)
Karel
--
Karel Zak <zakkr@zf.jcu.cz>
http://home.zf.jcu.cz/~zakkr/
C, PostgreSQL, PHP, WWW, http://docs.linux.cz, http://mape.jcu.cz