From: D'Arcy J.M. Cain <darcy@druid.net>
To: Kenneth Gonsalves <lawgon@thenilgiris.com>
Cc: tgl@sss.pgh.pa.us
Cc: talexb@gmail.com
Cc: pgsql-sql@postgresql.org
Subject: Re: parse error at or near "(" -- Huh???
Date: Mon, 13 Dec 2004 03:44:11 -0500
Message-ID: <20041213034411.76e3f470.darcy@druid.net> (raw)
In-Reply-To: <0412130927042G.21547@thenilgiris.com>
References: <f9870c010412091219495dbb8e@mail.gmail.com>
<14681.1102905949@sss.pgh.pa.us>
<0412130927042G.21547@thenilgiris.com>
On Mon, 13 Dec 2004 09:27:04 +0530
Kenneth Gonsalves <lawgon@thenilgiris.com> wrote:
> and while on this topic, how does one interpret the line numbers one
> gets when running psql -f to create tables?
Forget about line numbers. Add the -e option and your statements will
show up in your output. Here is a sample (Unix) command line that I
commonly use to run statements from a file:
psql table -f in.file -e > out.file 2>&1
Now I can search the file for "ERROR" and see exactly what preceded it.
--
D'Arcy J.M. Cain <darcy@druid.net> | Democracy is three wolves
http://www.druid.net/darcy/ | and a sheep voting on
+1 416 425 1212 (DoD#0082) (eNTP) | what's for dinner.
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-sql@postgresql.org
Cc: darcy@druid.net, lawgon@thenilgiris.com, tgl@sss.pgh.pa.us, talexb@gmail.com
Subject: Re: parse error at or near "(" -- Huh???
In-Reply-To: <20041213034411.76e3f470.darcy@druid.net>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox