| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Bruce Momjian <bruce(at)momjian(dot)us> |
| Cc: | "Jim C(dot) Nasby" <jim(at)nasby(dot)net>, Simon Riggs <simon(at)2ndquadrant(dot)com>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: psql return codes |
| Date: | 2006-12-06 19:25:46 |
| Message-ID: | 184.1165433146@sss.pgh.pa.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Bruce Momjian <bruce(at)momjian(dot)us> writes:
> Jim C. Nasby wrote:
>> Why should it matter if the "SELECT * FROM foo" came to
>> psql via -f or -c?
> Well, it explains exactly what Simon was seeing. I agree it is strange,
> but I was asking if Simon knew it was documented. I assume the "3" is
> used to report a different error from 'file not found' or something.
Well, the real point here is that ON_ERROR_STOP doesn't apply to
interactive input, and -c is evidently being considered to be
interactive. You could argue that either way I suppose, but seeing
that -c can only issue a single command, implementing ON_ERROR_STOP
for it seems like largely a waste of effort.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jeff Davis | 2006-12-06 19:37:32 | 8.2 bug with outer join reordering |
| Previous Message | Bruce Momjian | 2006-12-06 19:15:32 | Re: psql return codes |