Re: Appending \o output instead of overwriting the output file

From: Jasen Betts <jasen(at)xnet(dot)co(dot)nz>
To: pgsql-general(at)postgresql(dot)org
Subject: Re: Appending \o output instead of overwriting the output file
Date: 2009-02-19 11:30:31
Message-ID: gnjfsn$k71$3@reversiblemaps.ath.cx
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On 2009-02-18, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> John R Pierce <pierce(at)hogranch(dot)com> writes:
>> Tom Lane wrote:
>>> "Brent Wood" <b(dot)wood(at)niwa(dot)co(dot)nz> writes:
>>>> Perhaps \o+ as a future fix for this?
>
>>> I'd prefer "\o >>file" but maybe I'm too steeped in unix-isms.
>
>> \o+ is reasonably consistent with the other \ command usages...
>
> Not really; none of the other commands interpret + as meaning "append to
> an existing file". They tend to take it as meaning "do something *in
> addition to* what you normally do", not to do something that is
> significantly different from the base command.

Yes, also if \o already supports | why not other plumbing symbols
like >> and for completeness > (also possibly >& filedescriptor?)

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Oleg Bartunov 2009-02-19 12:04:01 Re: Accessing array elements in a FOR PL/pgsql loop
Previous Message Igor Katson 2009-02-19 11:26:56 Re: Accessing array elements in a FOR PL/pgsql loop