| From: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
|---|---|
| To: | pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: psql line number reporting from stdin |
| Date: | 2011-12-03 17:27:32 |
| Message-ID: | 1322933252.26266.3.camel@vanquo.pezone.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On lör, 2011-11-26 at 22:36 +0200, Peter Eisentraut wrote:
> There is a long-standing oddity in psql that running
>
> psql -f foo.sql
>
> returns error messages with file name and line number, like
>
> psql:foo.sql:1: ERROR: syntax error at or near "foo"
>
> but running
>
> psql < foo.sql does not. I suggest we change the latter to print
>
> psql:<stdin>:1: ERROR: syntax error at or near "foo"
It turns out that running
psql -f -
already used to print
psql:<stdin>:1: ERROR: blah
except that it got broken between 8.4 and 9.0 (commit b291c0fb), and now
prints
psql:-:1: ERROR: blah
I'll try to find a way to fix that and integrate it with the change I'm
proposing.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2011-12-03 17:53:19 | Re: why local_preload_libraries does require a separate directory ? |
| Previous Message | Heikki Linnakangas | 2011-12-03 16:37:14 | Re: Bug in walsender when calling out to do_pg_stop_backup (and others?) |