Re: Remove pg_dump -i option (was Re: Proposed patch: synchronized_scanning GUC variable)
От | Peter Eisentraut |
---|---|
Тема | Re: Remove pg_dump -i option (was Re: Proposed patch: synchronized_scanning GUC variable) |
Дата | |
Msg-id | 200801311613.56828.peter_e@gmx.net обсуждение исходный текст |
Ответ на | Remove pg_dump -i option (was Re: Proposed patch: synchronized_scanning GUC variable) (Alvaro Herrera <alvherre@commandprompt.com>) |
Ответы |
Re: Remove pg_dump -i option (was Re: Proposed
patch: synchronized_scanning GUC variable)
Re: Remove pg_dump -i option (was Re: Proposed patch: synchronized_scanning GUC variable) |
Список | 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 по дате отправления: