Re: COPY syntax improvement

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>
Cc: PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: COPY syntax improvement
Date: 2002-06-19 13:54:52
Message-ID: 3996.1024494892@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> writes:
> I have not modified pg_dump so that 7.3 dumps can be loaded into <=7.2
> databases. I have modified psql \copy to _only_ use the new syntax, and
> to only send the new syntax to the backends.

Why not leave psql alone? Seems to me you are gratuitously breaking
backwards compatibility of psql, and gaining absolutely zero in return.

I know that a lot of 7.3 psql's other backslash commands will not work
against pre-7.3 servers, but there's no help for that (short of making
psql version-aware like pg_dump is). I don't think that's a reason to
break \copy too, when there is no need for it.

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Hannu Krosing 2002-06-19 14:01:41 Re: SQL99 feature list
Previous Message Tom Lane 2002-06-19 13:47:04 Re: Why is CacheMemoryContext declared DLLIMPORT in one place and not in another?