From: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
---|---|
To: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
Cc: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: pg_dump no longer honors --no-reconnect |
Date: | 2003-09-29 08:07:57 |
Message-ID: | Pine.LNX.4.44.0309291004200.22870-100000@peter.localdomain |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
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(at)gmx(dot)net
From | Date | Subject | |
---|---|---|---|
Next Message | Andreas Pflug | 2003-09-29 09:04:38 | Re: ADD FOREIGN KEY (was Re: [GENERAL] 7.4Beta) |
Previous Message | Peter Eisentraut | 2003-09-29 08:03:09 | Re: more i18n/l10n issues |