From: | Michael Paquier <michael(dot)paquier(at)gmail(dot)com> |
---|---|
To: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
Cc: | Andres Freund <andres(at)2ndquadrant(dot)com>, Peter Eisentraut <peter_e(at)gmx(dot)net>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: moving from contrib to bin |
Date: | 2015-03-11 01:13:10 |
Message-ID: | CAB7nPqRS-=+g12QjZWDeujnQuOt_b6XZcVS5mO1RdzDAtXAnmw@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Wed, Mar 11, 2015 at 10:06 AM, Alvaro Herrera
<alvherre(at)2ndquadrant(dot)com> wrote:
> Michael Paquier wrote:
>> On Tue, Mar 10, 2015 at 10:48 PM, Alvaro Herrera
>> <alvherre(at)2ndquadrant(dot)com> wrote:
>
>> > How do we go about getting these patches pushed?
>>
>> I think that one of the last point raised (by Andres) was if the
>> Makefiles in src/bin should depend on pgxs.mk or not. FWIW, I think as
>> well that it should be a subsequent patch not related to this one as
>> it is a different debate to have stuff of src/bin depend on contrib
>> infrastructure.
>
> I don't think we care one bit whether these modules use pgxs, at least
> not currently. If we find any issues later on, it should be an easy fix
> anyway.
>
>> Now, the pushing plan was to have the stuff of pg_upgrade done in a
>> separate commit. Note that I am fine helping out wrapping up things
>> particularly on Windows if that helps.
>
> I vote for moving one module per commmit. Probably the first commit
> will be the hardest one to get right, so let's pick an easy module --
> say, pgbench. That way there are less gotchas hopefully. Once we have
> that working everywhere we look into moving another one.
Fine for me. You want a cross-OS patch?
--
Michael
From | Date | Subject | |
---|---|---|---|
Next Message | Robert Haas | 2015-03-11 01:57:33 | Re: proposal: searching in array function - array_position |
Previous Message | Alvaro Herrera | 2015-03-11 01:06:37 | Re: moving from contrib to bin |