|From:||"Daniel Verite" <daniel(at)manitou-mail(dot)org>|
|To:||"Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>|
|Cc:||"Fabien COELHO" <coelho(at)cri(dot)ensmp(dot)fr>,"Alvaro Herrera" <alvherre(at)2ndquadrant(dot)com>,"PostgreSQL Hackers" <pgsql-hackers(at)lists(dot)postgresql(dot)org>,"David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>|
|Subject:||Re: Alternative to \copy in psql modelled after \g|
|Views:||Raw Message | Whole Thread | Download mbox|
Tom Lane wrote:
> A variant that might or might not be safer is "\g <foo", ie we
> insist on you putting a mark there that shows you intended to read.
> Also, not quite clear what we'd do about copy-from-program.
> I think "\g |foo" is definitely confusing for that. "\g foo|"
> would be better if it doesn't have syntax issues.
I haven't written any patch yet, but I was thinking of submitting
something like that, with the addition of "\g >foo" as a synonym of
"\g foo" for the symmetry with "<".
Perl's open() also uses the "program |" syntax.
PostgreSQL-powered mailer: http://www.manitou-mail.org
|Next Message||Amit Langote||2019-01-28 15:28:43||Re: Rename nodes/relation.h => nodes/pathnodes.h ?|
|Previous Message||Tom Lane||2019-01-28 15:18:48||Rename nodes/relation.h => nodes/pathnodes.h ?|