On Thu, Mar 22, 2018 at 11:07:48AM -0400, Robert Haas wrote:
> I suppose we could provide a build-time option to change this behavior.
it seems to me that it is going to be hard to reach a consensus by the
end of the commit fest, so I am marking this patch as returned with
feedback. Not sure if
On Wed, Mar 21, 2018 at 11:43 PM, Michael Paquier wrote:
> On Wed, Mar 07, 2018 at 05:06:59PM -0500, Robert Haas wrote:
>> TBH I find that Homebrew example pretty odd. I would understand
>> installing each major release in a version directory, but putting
>> every point
Michael Paquier writes:
> The last complain on the matter I can find actually involves the same
> people as this thread :)
> https://www.postgresql.org/message-id/54DE457F.2090206%40gmx.net
> So the patch should be marked as rejected or at least returned with
> feedback?
On Wed, Mar 07, 2018 at 05:06:59PM -0500, Robert Haas wrote:
> TBH I find that Homebrew example pretty odd. I would understand
> installing each major release in a version directory, but putting
> every point release in a different versioned directory seems like a
> bad plan.
That's a project
On Wed, Feb 28, 2018 at 9:34 PM, Peter Eisentraut
wrote:
> Except ... this doesn't actually work. find_my_exec() resolves symlinks
> to find the actual program installation, and so for example the
> installed initdb will look for postgres in src/bin/initdb/. I