| From: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
|---|---|
| To: | Aman Rathi <aman(dot)rathi0904(at)gmail(dot)com> |
| Cc: | PostgreSQL www <pgsql-www(at)postgresql(dot)org> |
| Subject: | Re: Fwd: Psql.exe error logging |
| Date: | 2016-02-26 15:21:19 |
| Message-ID: | CAKFQuwaxGeF2g_+-ZRATprpT0s4bc=PCf9PEy6+VhpvJBdTEFg@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-www |
On Fri, Feb 26, 2016 at 7:36 AM, David G. Johnston <
david(dot)g(dot)johnston(at)gmail(dot)com> wrote:
> On Fri, Feb 26, 2016 at 4:29 AM, Aman Rathi <aman(dot)rathi0904(at)gmail(dot)com>
> wrote:
>
>> Hi David,
>>
>> Thanks for the reply, but it still doesn't seem to run.
>>
>> I followed the following steps:
>> 1) updated the on_error_stop value to 1
>>
>> [image: Inline image 1]
>>
>
>> 2) Ran a command that should fail and exit
>>
>> [image: Inline image 1]
>>
>>
> Any particular reason you didn't just add the --set option from #1 to the
> psql command in #2?
>
>
>
As an aside, the portion of the command "psql -c -a -f <file>" is wrong
(though apparently not broken...). You specify, via "c", that you are
going to provide a single command for psql to execute but then fail to
provide any such command and instead change you mind and tell it your are
going to provide a script file, via "f", instead.
David J.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Melvin Davidson | 2016-02-26 15:59:53 | Re: Fwd: Psql.exe error logging |
| Previous Message | David G. Johnston | 2016-02-26 14:36:24 | Re: Fwd: Psql.exe error logging |