Re: generic copy options - Mailing list pgsql-hackers

From Emmanuel Cecchet
Subject Re: generic copy options
Date
Msg-id 4AB232F1.9020207@asterdata.com
Whole thread Raw
In response to Re: generic copy options  (Pavel Stehule <pavel.stehule@gmail.com>)
Responses Re: generic copy options
List pgsql-hackers
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).

manu


pgsql-hackers by date:

Previous
From: Pavel Stehule
Date:
Subject: Re: generic copy options
Next
From: Robert Haas
Date:
Subject: Re: Linux LSB init script