Gregory Stark <stark@enterprisedb.com> writes:
> "David Fetter" <david@fetter.org> writes:
>> What's the reasoning behind \c&? Does it "send things into the
>> background" the way & does in the shell?
> Sort of. It sends the *subsequent* command to the background...
That sounds just bizarre. Existing backslash commands that do something
to a SQL command are typed *after* the command they affect (\g for
instance). I don't think you should randomly change that.
regards, tom lane