Re: proposal: multiple psql option -c

From: Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>
To: Rosser Schwarz <rosser(dot)schwarz(at)gmail(dot)com>
Cc: Fabrízio Mello <fabriziomello(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: proposal: multiple psql option -c
Date: 2015-07-16 21:16:47
Message-ID: CAFj8pRDnO+Q7m7yTU22O8FDccpuS7n2xvKJi=yMfvFuTvjHy0Q@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

2015-07-16 23:10 GMT+02:00 Rosser Schwarz <rosser(dot)schwarz(at)gmail(dot)com>:

> On Thu, Jul 16, 2015 at 1:44 PM, Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>
> wrote:
>
>> 2015-07-16 22:07 GMT+02:00 Fabrízio de Royes Mello <
>> fabriziomello(at)gmail(dot)com>:
>>
>>> Why you want it if we already have the -f option that cover this use
>>> case?
>>>
>> It doesn't help me - we would to run script or remote script (via ssh)
>> without necessity to create (and later drop) files on production servers.
>>
>
> Does piping a series of commands into psql work in your scenario? You can
> even say things like:
>
> cat $local_file | ssh $production_server 'psql $database'
>

probably not - the first remote command is sudo su - due security reasons

>
> --
> :wq
>

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message dinesh kumar 2015-07-16 22:03:57 Re: proposal: multiple psql option -c
Previous Message Rosser Schwarz 2015-07-16 21:10:36 Re: proposal: multiple psql option -c