Обсуждение: Compiling without libpq
Hello, what is the difference in compiling with or without libpq? I understand that without libpq is convenient if you do not have PostgreSQL installed on the system, but then why would I want to compile with libpq? I see in configure script that openssl is disabled if I compile without libpq. Why is that and what functionality do I loose exactly? The reason I am asking is that I would like to make a package for it for Haiku and I would like to know if is worth it to see if I need to create two packages (one for users who have PostgreSQL installed and one for those without it). Thanks for any help, Mark Hellegers -- Spangalese for beginners `Geh nae?' `Do you know the serial number on the bumper of that 1958 Thunderbird?'
On 06/15/2015 11:27 AM, Mark Hellegers wrote: > > Hello, > > what is the difference in compiling with or without libpq? As I recall you lose extended auth capability (no ldap for example) and you lose the ability to have encrypted connections. > I see in configure script that openssl is disabled if I compile without > libpq. Why is that and what functionality do I loose exactly? See my comment about encrypted connections above. JD > -- Command Prompt, Inc. - http://www.commandprompt.com/ 503-667-4564 PostgreSQL Centered full stack support, consulting and development. Announcing "I'm offended" is basically telling the world you can't control your own emotions, so everyone else should do it for you.
On Tue, Jun 16, 2015 at 3:27 AM, Mark Hellegers <mark@firedisk.net> wrote: > Hello, > > what is the difference in compiling with or without libpq? > I understand that without libpq is convenient if you do not have > PostgreSQL installed on the system, but then why would I want to > compile with libpq? > I see in configure script that openssl is disabled if I compile without > libpq. Why is that and what functionality do I loose exactly? > The reason I am asking is that I would like to make a package for it > for Haiku and I would like to know if is worth it to see if I need to > create two packages (one for users who have PostgreSQL installed and > one for those without it). Note that Postgres ODBC has a hard dependency with libpq on HEAD because the things at protocol level that were used in the driver are basically duplicates of what the libpq routines offer. Hence you may want to compile with libpq in your packages to be in-line with the next version to be released. -- Michael
> On Tue, Jun 16, 2015 at 3:27 AM, Mark Hellegers <mark@firedisk.net> > wrote: > > Hello, > > > > what is the difference in compiling with or without libpq? > > I understand that without libpq is convenient if you do not have > > PostgreSQL installed on the system, but then why would I want to > > compile with libpq? > > I see in configure script that openssl is disabled if I compile > > without > > libpq. Why is that and what functionality do I loose exactly? > > The reason I am asking is that I would like to make a package for > > it > > for Haiku and I would like to know if is worth it to see if I need > > to > > create two packages (one for users who have PostgreSQL installed > > and > > one for those without it). > > Note that Postgres ODBC has a hard dependency with libpq on HEAD > because the things at protocol level that were used in the driver are > basically duplicates of what the libpq routines offer. Hence you may > want to compile with libpq in your packages to be in-line with the > next version to be released. Thank you and Joshua for the feedback. I will create one package compiled with libpq then. Kind regards, Mark Hellegers -- Spangalese for beginners `Rangleugar mho shwarma.' `Your Christmas elf is on fire.'