Jim Nasby wrote: > On 2/5/16 10:08 AM, David Fetter wrote: > >On Wed, Feb 03, 2016 at 06:02:57PM -0600, Jim Nasby wrote: > >>I just discovered that ./configure will happily accept '--with-pgport=' (I > >>was actually doing =$PGPORT, and didn't realize $PGPORT was empty). What you > >>end up with is a compile error in guc.c, with no idea why it's broken. Any > >>reason not to have configure or at least make puke if pgport isn't valid? > > > >That seems like a good idea. > > Patch attached. I've verified it with --with-pgport=, =0, =77777 and =1. It > catches what you'd expect it to.
Does it work to specify port numbers below 1024? -- Álvaro Herrera http://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
