From: | "Dave Page" <dpage(at)pgadmin(dot)org> |
---|---|
To: | "Peter Eisentraut" <peter_e(at)gmx(dot)net> |
Cc: | pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: libpq.rc make rule |
Date: | 2008-02-25 22:33:33 |
Message-ID: | 937d27e10802251433u4820d510o82f2a925ac064cb@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Mon, Feb 25, 2008 at 10:03 PM, Peter Eisentraut <peter_e(at)gmx(dot)net> wrote:
> Dave Page wrote:
> > It's used on Windows to ensure that installers can do the right thing
> > when replacing a copy of libpq.dll. The daily build number was the
> > most maintenance-free way of getting a fourth value for the version
> > resource.
>
> Isn't that what the shared library version numbers are for? Do you need finer
> resolution than that?
Yes, because newer builds may be linked against updated runtime
versions. We need to be sure the installer will upgrade the file so it
definitely matches any runtimes (or other dependencies) that we're
also installing/upgrading.
--
Dave Page
EnterpriseDB UK: http://www.enterprisedb.com
The Oracle-compatible database company
From | Date | Subject | |
---|---|---|---|
Next Message | Andrew Dunstan | 2008-02-25 23:11:15 | Re: idea: simple variadic functions in SQL and PL/pgSQL |
Previous Message | Joshua D. Drake | 2008-02-25 22:11:16 | Re: 8.3 / 8.2.6 restore comparison |