Re: [HACKERS] pg_dump no longer honors --no-reconnect

2003-09-29 Thread Tom Lane
Peter Eisentraut <[EMAIL PROTECTED]> writes: > 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.) Yes, because "SET SESSION AUTHORIZATION yourself" is allowed

Re: [HACKERS] pg_dump no longer honors --no-reconnect

2003-09-29 Thread Bruce Momjian
Tom Lane wrote: > > Yes, but didn't the old code prompt you for passwords, or silently work > > if you had things set to 'trust', while our new code requires > > super-user? > > If you have things set to "trust", you can be superuser, eh? > > A password approach might be workable using ~/.pgpass,

Re: [HACKERS] pg_dump no longer honors --no-reconnect

2003-09-29 Thread Tom Lane
Bruce Momjian <[EMAIL PROTECTED]> writes: > Peter Eisentraut wrote: >> 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.) > Yes, but didn't the old code pro

Re: [HACKERS] pg_dump no longer honors --no-reconnect

2003-09-29 Thread Bruce Momjian
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

Re: [HACKERS] pg_dump no longer honors --no-reconnect

2003-09-29 Thread Tom Lane
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'

Re: [HACKERS] pg_dump no longer honors --no-reconnect

2003-09-29 Thread Bruce Momjian
Peter Eisentraut wrote: > 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 neve

Re: [HACKERS] pg_dump no longer honors --no-reconnect

2003-09-29 Thread Peter Eisentraut
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 th