Re: pg_upgrade versus MSVC build scripts

From: Andrew Dunstan <andrew(at)dunslane(dot)net>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: pg_upgrade versus MSVC build scripts
Date: 2010-05-12 19:21:08
Message-ID: 4BEAFFA4.7050600@dunslane.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Tom Lane wrote:
> Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org> writes:
>
>> Excerpts from Tom Lane's message of mié may 12 14:07:13 -0400 2010:
>>
>>> We could try to make this a supported build arrangement, but I'm
>>> inclined to think that a cleaner solution is to split out the loadable
>>> module as a separate contrib subdirectory. Thoughts?
>>>
>
>
>> Do you mean contrib/pg_upgrade/somelib? If so, +1.
>>
>
> Hmm. I had been thinking the other way, but I'll see if that can be
> made to work.
>
>
>

Not sure this will work on its own with the MSVC build system - I don't
think it's set up for sub-modules. But we can finessee that if
necessary, just as we make special provision for pgcrypto.

cheers

andrew

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Robert Haas 2010-05-12 19:23:27 Re: primary/secondary/master/slave/standby
Previous Message Robert Haas 2010-05-12 19:20:35 comment needs to be updated for HS?