Re: generic copy options
От | Pavel Stehule |
---|---|
Тема | Re: generic copy options |
Дата | |
Msg-id | 162867790909170703t288929dcw76ff8af777991985@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: generic copy options (Emmanuel Cecchet <manu@asterdata.com>) |
Список | pgsql-hackers |
2009/9/17 Emmanuel Cecchet <manu@asterdata.com>: > Pavel Stehule wrote: >>> >>> Well, I wonder how many users just upgrade psql vs upgrade the server. I >>> was >>> thinking that when users perform a database upgrade their application >>> often >>> remain the same and therefore the server needs to support the old syntax. >>> Unless you are upgrading a machine where a bunch of psql-based scripts >>> are >>> running to update various remote Postgres instances with older versions, >>> I >>> would guess that it is unlikely that someone is going to upgrade psql and >>> keep the old instance of the server on the same machine. >>> I just wonder how many users are using a single psql to manage multiple >>> server instances of different older versions. >>> >> >> What application, that use current copy format for fast data import? I >> thing, so doing incompatible changes of copy statement syntax is very >> bad idea. >> > > The old syntax is still supported in both psql and the server but I am not > sure how many applications are relying on psql to perform a copy operation > (actually a \copy). who knows. \copy is very useful thinks and people who imports data from local use it. I am sure, so this feature is often used, mainly by unix dba. regards Pavel > > manu >
В списке pgsql-hackers по дате отправления: