Re: "COPY foo FROM STDOUT" and ecpg

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-27 11:33:44
Message-ID: 20130227113344.GA15486@feivel.credativ.lan
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Tue, Feb 26, 2013 at 07:24:44PM +0200, Heikki Linnakangas wrote:
> >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.
>
> Just less code to maintain. And it's strange to forbid something in
> ecpg grammar that the backend accepts, as a matter of principle.

Na, I was talking about copying from STDOUT and to STDIN. Even if this is a
very old "feature" I think we should fix 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

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Heikki Linnakangas 2013-02-27 12:54:53 Re: [COMMITTERS] pgsql: Fix pg_dumpall with database names containing =
Previous Message Ivan Lezhnjov IV 2013-02-27 11:11:40 Re: backup.sgml patch that adds information on custom format backups