On Mon, Oct 10, 2005 at 06:25:59PM -0700, John Shin wrote:
Is that the exact command you ran? As shown it should fail with a
syntax error because the options are in the wrong place:

% createdb test -h localhost -U postgres
createdb: too many command-line arguments (first is "localhost")
Try "createdb --help" for more information.

Likewise:

% createlang plpgsql test -h localhost -U postgres
createlang: too many command-line arguments (first is "-h")
Try "createlang --help" for more information.

Use the --help option or consult the createlang documentation to see
the correct order of options and arguments. It works fine here with
..pgpass if the syntax is correct; have you run "createlang --version"
to verify that you're running the 8.0.4 version?

--
Michael Fuhr

---------------------------(end of broadcast)---------------------------
TIP 4: Have you searched our list archives?

http://archives.postgresql.org

[Please copy the mailing list on replies so others can participate
in and learn from the discussion.]

On Tue, Oct 11, 2005 at 11:16:40AM -0700, John Shin wrote:
[snip]

Hmmm...this command fails with "too many command-line arguments"
on both FreeBSD and Solaris (8.0.4 built from source on both), so
I wonder if your build is using a getopt_long() that behaves
differently than what I'm using. Might not matter, though.

Have you done a process trace (strace, ktrace, truss, etc.) to see
if createlang is even looking for .pgpass? Does it work if you
set the PGUSER environment variable instead of using the -U option?

You mentioned FC4, so maybe Tom Lane or somebody more familiar
with that platform has some ideas about what's happening.

--
Michael Fuhr

---------------------------(end of broadcast)---------------------------
TIP 5: don't forget to increase your free space map settings

Michael Fuhr <mike (AT) fuhr (DOT) org> writes:
That syntax does work for me on FC4, so probably the issue is GNU
getopt_long versus other implementations (likely, our own port/ code).
I don't think it's relevant though, since John exhibited a failure
even while using the "standard" command line syntax.

The whole thing is more than passing strange. createlang uses exactly
the same connection code as the other "scripts" binaries, so there's
no obvious reason why it would behave differently. I concur with the
suggestion to try strace'ing it and see where the behavior starts to
vary from, say, createdb.

regards, tom lane

---------------------------(end of broadcast)---------------------------
TIP 5: don't forget to increase your free space map settings