Christian Goetze <cg@xxxxxxxxxxx> writes: >>> pg_restore: [archiver] WARNING: skipping large-object restoration >> >> IIRC, you get that if you're asking it to emit a text script rather than >> connect directly to the destination database server. I think you need a >> "-d databasename" switch to make that happen. > Does this mean that the only way to upgrade is to have both the old and > the new databases running _at the same time_? No, unless you were hoping to pipe the output of pg_dump straight into pg_restore or something like that. > BTW, on further inspection, it would seem that the bytea fields loaded > properly after all - is the warning just a bug, or are "large objects" > something else altogether? AFAICS, the warning only comes out if there are large objects in the dump file (and no, these have nothing to do with bytea fields). regards, tom lane ---------------------------(end of broadcast)--------------------------- TIP 5: don't forget to increase your free space map settings
