Re: [OT] MySQL is bad, but THIS bad?

From: Andreas Pflug <pgadmin(at)pse-consulting(dot)de>
To: Martijn van Oosterhout <kleptog(at)svana(dot)org>
Cc: Mark Woodward <pgsql(at)mohawksoft(dot)com>, "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com>, "Jim C(dot) Nasby" <jnasby(at)pervasive(dot)com>, John DeSoi <desoi(at)pgedit(dot)com>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: [OT] MySQL is bad, but THIS bad?
Date: 2006-05-19 15:52:02
Message-ID: 446DE9A2.20002@pse-consulting.de
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-advocacy pgsql-hackers

Martijn van Oosterhout wrote:

> The biggest headache I find with using postgres is that various GPL
> licenced programs have trouble directly shipping postgresql support
> because of our use of OpenSSL. Each and every one of those program
> needs to add an exception to their licence for distributors to
> distribute postgresql support.

They could distribute a non-ssl-enabled version, *if* they really need
to include libpq in the package, or advise to to replace it with the
common version if ssl is required. I bet >99 % of pgsql connections are
not encrypted anyway.

Regards,
Andreas

In response to

Browse pgsql-advocacy by date

  From Date Subject
Next Message Joshua D. Drake 2006-05-19 15:59:43 Re: [HACKERS] Toward A Positive Marketing Approach.
Previous Message Martijn van Oosterhout 2006-05-19 15:38:21 Re: [OT] MySQL is bad, but THIS bad?

Browse pgsql-hackers by date

  From Date Subject
Next Message Jeff Frost 2006-05-19 15:53:51 Re: does wal archiving block the current client connection?
Previous Message Tom Lane 2006-05-19 15:49:18 Re: does wal archiving block the current client connection?