Bruce Momjian writes:
> Seems we can silently ignore a --use-set-session-authorization flag
> because that is now the default, but I don't see how we can ignore a
> --no-reconnect flag --- we should throw an error.
Why? The new bevavior of pg_dump is to never reconnect -- exactly the
point of this change.
> Also, the 7.3 manual mentions that only the super-user can restore using
> --use-set-session-authorization. This is now the only way to create
> dumps. Seems this is a new limitation to pg_dump that we didn't
> discuss.
It had been dicussed on and off for quite some time. This limitation
should only apply if you create dumps that contain objects owned by more
than one user. (Does it? I didn't check.)
--
Peter Eisentraut peter_e@gmx.net