Re: Sanity checking for ./configure options?

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: David Fetter <david(at)fetter(dot)org>
Cc: Jim Nasby <Jim(dot)Nasby(at)bluetreble(dot)com>, Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>, Pg Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Sanity checking for ./configure options?
Date: 2016-02-26 11:25:23
Message-ID: CA+TgmoaD+oyPGky12JAMNR5M+dUuyN8W-T+U+C5dfC+WFMkdYw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Wed, Feb 24, 2016 at 4:01 AM, David Fetter <david(at)fetter(dot)org> wrote:
> I'm thinking that both the GUC check and the configure one should
> restrict it to [1024..65535].

Doesn't sound like a good idea to me. If somebody has a reason they
want to do that, they shouldn't have to hack the source code and
recompile to make it work.

--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Васильев Дмитрий 2016-02-26 12:41:22 Relation cache invalidation on replica
Previous Message Amit Kapila 2016-02-26 11:19:04 Re: Prepared Statement support for Parallel query