| From: | Michael Meskes <meskes(at)postgresql(dot)org> |
|---|---|
| To: | Heikki Linnakangas <hlinnakangas(at)vmware(dot)com> |
| Cc: | PostgreSQL-development <pgsql-hackers(at)postgreSQL(dot)org> |
| Subject: | Re: "COPY foo FROM STDOUT" and ecpg |
| Date: | 2013-02-26 16:58:21 |
| Message-ID: | 20130226165821.GA25922@feivel.credativ.lan |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Tue, Feb 26, 2013 at 05:13:38PM +0200, Heikki Linnakangas wrote:
> COPY foo FROM STDOUT
> COPY foo TO STDIN
Does this make sense?
> Any particular reason for ecpg to check that, while the backend
> doesn't care? I think we should just remove those checks from the
> ecpg grammar.
IIRC this check was added because the check for "COPY FROM STDIN" had to added
anyway. Since you left that one in, the patch is fine by me, although I still
don't see a reason for it.
Michael
--
Michael Meskes
Michael at Fam-Meskes dot De, Michael at Meskes dot (De|Com|Net|Org)
Michael at BorussiaFan dot De, Meskes at (Debian|Postgresql) dot Org
Jabber: michael.meskes at gmail dot com
VfL Borussia! Força Barça! Go SF 49ers! Use Debian GNU/Linux, PostgreSQL
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Eisentraut | 2013-02-26 17:02:48 | Re: pg_xlogdump |
| Previous Message | Heikki Linnakangas | 2013-02-26 16:50:37 | Re: "COPY foo FROM STDOUT" and ecpg |