libpq naming on Win64
in [PgSql]
|
Prev: global\pg_auth
Next: execute sql commands in core
From: Hiroshi Inoue on 7 Jan 2010 07:21 Dave Page wrote: > On Thu, Jan 7, 2010 at 3:58 AM, Hiroshi Inoue <inoue(a)tpf.co.jp> wrote: >> Maybe I'm missing the point and have a question. >> >> For example, do 32bit psql and the 64bit one have the same name? >> If so, where will they be installed? > > I'm only talking about libpq. I see no reason to have 32 & 64 bit > versions of other utilities installed in parallel. Well what about the libraries (e.g openssl) libpq links? regards, Hiroshi Inoue -- Sent via pgsql-hackers mailing list (pgsql-hackers(a)postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
From: Dave Page on 7 Jan 2010 07:28
On Thu, Jan 7, 2010 at 12:21 PM, Hiroshi Inoue <inoue(a)tpf.co.jp> wrote: > Dave Page wrote: >> >> On Thu, Jan 7, 2010 at 3:58 AM, Hiroshi Inoue <inoue(a)tpf.co.jp> wrote: >>> >>> Maybe I'm missing the point and have a question. >>> >>> For example, do 32bit psql and the 64bit one have the same name? >>> If so, where will they be installed? >> >> I'm only talking about libpq. I see no reason to have 32 & 64 bit >> versions of other utilities installed in parallel. > > Well what about the libraries (e.g openssl) libpq links? Yes, that is an issue as I noted earlier. We probably would still have to put the 32 bit and 64 bit libraries in a different directory because of their naming conventions. -- Dave Page EnterpriseDB UK: http://www.enterprisedb.com -- Sent via pgsql-hackers mailing list (pgsql-hackers(a)postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers |