> >
> > Good advice. I turned on –verbose, and got a ton of output, ending with:
> >
> > pg_restore: setting owner and privileges for FK CONSTRAINT
> > user_id_refs_id_7ceef80f
> >
> > pg_restore: setting owner and privileges for FK CONSTRAINT
> > user_id_refs_id_dfbab7d
> >
> > pg_restore: [archiver (db)] could not execute query: no connection to
> > the server
> >
> > Command was: -- Completed on 2013-09-09 11:35:16 EDT
> >
> > pg_restore: [archiver (db)] could not execute query: no connection to
> > the server
This was a red herring. That last constraint that was listed is the last thing
in the dump/restore (at least according to --list). Perhaps at the end of
pg_restore, it's trying to send the comment to the database ("completed on...")
and that's confusing things? It does appear that the entire database has been
restored, but the cluster restart is disconcerting.
>
>
> At this point I would be more worried about the above, 'no connection to
> server'.
Yep, that would be the point where the cluster is restarting.
> --no-owner does not mean that ownership is not set, just that the ownership
> from the source database is not carried over.
>
> http://www.postgresql.org/docs/9.2/interactive/app-pgrestore.html
>
> -O
> --no-owner
> Do not output commands to set ownership of objects to match the original
> database. By default, pg_restore issues ALTER OWNER or SET SESSION
> AUTHORIZATION statements to set ownership of created schema elements.
> These statements will fail unless the initial connection to the database is
> made by a superuser (or the same user that owns all of the objects in the
> script). With -O, any user name can be used for the initial connection, and
> this user will own all the created objects.
Does this mean that the --no-owner is a command flag for pg_dump, but is
ignored by pg_restore? Let me run a test and see...
Disclaimer
THIS IS A CONFIDENTIAL COMMUNICATION. The information contained in this e-mail
is attorney-client privileged and confidential, intended only for the use of
the individual or entity named above. If the reader of this message is not the
intended recipient, or the employee or agent responsible to deliver it to the
intended recipient, you are here by notified that any dissemination,
distribution or copying of this communication is strictly prohibited. If you
have received this communication in error, please notify us immediately by
reply e-mail or by telephone (908) 233-8500.Thank you..
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
