Re: Remove pg_dump -i option (was Re: Proposed patch: synchronized_scanning GUC variable) - Mailing list pgsql-hackers

From Peter Eisentraut
Subject Re: Remove pg_dump -i option (was Re: Proposed patch: synchronized_scanning GUC variable)
Date
Msg-id 200801311613.56828.peter_e@gmx.net
Whole thread Raw
In response to Remove pg_dump -i option (was Re: Proposed patch: synchronized_scanning GUC variable)  (Alvaro Herrera <alvherre@commandprompt.com>)
Responses Re: Remove pg_dump -i option (was Re: Proposed patch: synchronized_scanning GUC variable)  (Bruce Momjian <bruce@momjian.us>)
Re: Remove pg_dump -i option (was Re: Proposed patch: synchronized_scanning GUC variable)  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
Am Donnerstag, 31. Januar 2008 schrieb Alvaro Herrera:
> Effect: we would stop receiving complaints that an old pg_dump can talk
> to a server that most likely is incompatible with it.  People would
> learn on the spot that they must install the newer pg_dump.

I think a more moderate measure might be to clarify the error message

"aborting because of version mismatch  (Use the -i option to proceed 
anyway.)\n"

I'm not sure how many of the mentioned complaints we are getting, but the 
error message might make people think that it's complaining because the 
versions are not equal rather than that the versions are known not 
compatible.

-- 
Peter Eisentraut
http://developer.postgresql.org/~petere/


pgsql-hackers by date:

Previous
From: Dimitri Fontaine
Date:
Subject: Re: {**Spam**} Re: [PATCHES] Proposed patch: synchronized_scanning GUC variable
Next
From: Bruce Momjian
Date:
Subject: Re: {**Spam**} Re: [PATCHES] Proposed patch: synchronized_scanning GUC variable