From: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: COPY syntax improvement |
Date: | 2002-06-19 16:32:01 |
Message-ID: | 200206191632.g5JGW1u09582@candle.pha.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Tom Lane wrote:
> 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.
Yes, it was too late last night to think. I have made \copy
backward-compatible, and it internally uses the old syntax.
> 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.
Yep.
--
Bruce Momjian | http://candle.pha.pa.us
pgman(at)candle(dot)pha(dot)pa(dot)us | (610) 853-3000
+ If your life is a hard drive, | 830 Blythe Avenue
+ Christ can be your backup. | Drexel Hill, Pennsylvania 19026
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2002-06-19 16:35:46 | Re: ecpg and bison again |
Previous Message | Bruce Momjian | 2002-06-19 16:00:40 | Re: ecpg and bison again |