Tom Lane wrote: > Bruce Momjian <[EMAIL PROTECTED]> writes: > > but I don't see how we can ignore a --no-reconnect flag --- we should > > throw an error. > > We can ignore it because we don't reconnect. I only took out the flag > because I noticed it was no longer tested anywhere after I removed the > \connect code paths. I'm not sure if the old docs mentioned that > --no-reconnect was irrelevant when using set-session-authorization, > but that's how the code behaved. > > > 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. > > No, because a non-superuser can still restore with --no-owner; which is > actually a step forward over what he could have done with a \connect script. > (Unless you think that the scenario of a non-superuser who knows > everyone's password is something pg_dump needs to cater to.)
Oh, OK, thanks. My initial mistake was reading --no-reconnect as --reconnect; not sure how I did that. -- Bruce Momjian | http://candle.pha.pa.us [EMAIL PROTECTED] | (610) 359-1001 + If your life is a hard drive, | 13 Roberts Road + Christ can be your backup. | Newtown Square, Pennsylvania 19073 ---------------------------(end of broadcast)--------------------------- TIP 2: you can get off all lists at once with the unregister command (send "unregister YourEmailAddressHere" to [EMAIL PROTECTED])
