| 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: | Melvin Davidson <melvin6925(at)gmail(dot)com>, PostgreSQL www <pgsql-www(at)postgresql(dot)org> |
| Subject: | Re: Fwd: Psql.exe error logging |
| Date: | 2016-02-29 07:24:07 |
| Message-ID: | CAKFQuwa+0O2VKaAfqbR3iOXTEoQKzTR13+6RQ_=hRF0DSVKOHQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-www |
On Monday, February 29, 2016, Aman Rathi <aman(dot)rathi0904(at)gmail(dot)com> wrote:
> Hi David,
>
> 1) I thought that --set command is meant at DB level for all the commands
> being run. So ran it first. Not sure how to use it within the command.
>
>
everyone else is bottom posting. Please do the same.
On the point above: everytime you execute psql you connect to the database
using a clean session. Nothing carries over between sessions. So while
--set alters the session you have to make you specify it on the psql
invocation you actually want to have stop on errors.
David J.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Craig Ringer | 2016-02-29 08:28:23 | Re: Fwd: Psql.exe error logging |
| Previous Message | Aman Rathi | 2016-02-29 07:11:34 | Re: Fwd: Psql.exe error logging |