Skip site navigation (1) Skip section navigation (2)

Re: BUG #2495: -i start up option blows pg_ctl program.

From: Alvaro Herrera <alvherre(at)commandprompt(dot)com>
To: Ermest <whitelaw(at)netc(dot)pt>
Cc: pgsql-bugs(at)postgresql(dot)org
Subject: Re: BUG #2495: -i start up option blows pg_ctl program.
Date: 2006-06-24 02:23:06
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-bugs
Ermest wrote:

> When I attempt to configure postgres to allow tcpip connections by adding
> the -i option at startup, pg_ctl bombs by referencing address 0x0000.  The
> -i is added to the service startup parameters via the Registry.

There is indeed a bug in pg_ctl here.  We are reporting an error which
getopt_long already reported; and furthermore, optarg is not set by that
function in case of error.  This is the fix:

        while ((c = getopt_long(argc, argv, "D:l:m:N:o:p:P:sU:wW", long_options, &option_index)) != -1)
            switch (c)
                case default:
-                   write_stderr(_("%s: invalid option %s\n"), progname, optarg);

> I note also,"tcpip_socketi does not appear in installed postgresql.conf   
> Adding tcpip_socket=true had no effect on the -i bomb out.

No, the tcpip_socket option was removed in 8.0.  Use listen_interfaces

Alvaro Herrera                      
PostgreSQL Replication, Consulting, Custom Development, 24x7 support

In response to


pgsql-bugs by date

Next:From: Tom LaneDate: 2006-06-24 03:32:05
Subject: Re: BUG #2495: -i start up option blows pg_ctl program.
Previous:From: ErmestDate: 2006-06-23 21:41:37
Subject: BUG #2495: -i start up option blows pg_ctl program.

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group