Re: pg_upgrade versus MSVC build scripts

From: Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: pg_upgrade versus MSVC build scripts
Date: 2010-05-12 19:10:47
Message-ID: 1273691327-sup-5352@alvh.no-ip.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

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. If you instead mean
putting the library in contrib/somelib, I'm not so sure that it's
cleaner than trying to support executable+shared lib in a single contrib
module.
--

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2010-05-12 19:12:14 Re: pg_upgrade versus MSVC build scripts
Previous Message Stefan Kaltenbrunner 2010-05-12 19:10:28 Re: max_standby_delay considered harmful