Re: Fwd: Re: enabling postgresql by default - Mailing list pgsql-advocacy

From scott.marlowe
Subject Re: Fwd: Re: enabling postgresql by default
Date
Msg-id Pine.LNX.4.33.0306241009510.27167-100000@css120.ihs.com
Whole thread Raw
In response to Re: Fwd: Re: enabling postgresql by default  (Robert Treat <xzilla@users.sourceforge.net>)
Responses Re: Fwd: Re: enabling postgresql by default  (Evil Azrael <evilazrael@evilazrael.de>)
List pgsql-advocacy
On 24 Jun 2003, Robert Treat wrote:

> On Tue, 2003-06-24 at 11:36, scott.marlowe wrote:
> <snip/reorder>
> > Rather than include ANY interface, I think it would be wiser to only use
> > the connect libs that are already on a server.  I got the feeling Sterling
> > agreed with me on that point, by the way.
> >
>
> Given that Sterling recommend the inclusion of sqlite as a default, i
> don't see that's how you came to that conclusion...

He informed us it was happening, I don't think it was necessarily his
idea.  If you read the earlier posts in this thread, you'll see he was
against inclusion of MySQL's connect libs as well.

> > But my argument is that NOTHING should be enabled "by default" unless it
> > already has connection libraries.  Including a static (i.e. not updated
> > when postgresql gets updated) connection library is a bad thing, since any
> > bug in the connection lib will live on in the staticly linked connection
> > code shipped with PHP.
> >
> > If the connection libs for DB2, Oracle, and Postgresql are found on the
> > machine, then PHP should autoconfigure to use them.  If they're not there,
> > then including them in the php distro is short sighted and likely to cause
> > as many problems as it fixes.
> >
> > Keep in mind that including the MySQL libs with PHP was a mixed bag, since
> > using a different mysql connect lib for PHP and another for apache if you
> > use mod_auth_mysql would result in a crashing server situation that was
> > suboptimal.
> >
>
> All of which are valid view points, but I think miss the mark since the
> php guys seem to have moved past the point of deciding "if something
> should be included" and are now deciding "what will be included".
>
> If they want to level the playing field and not include anything I am
> fine with that, and I think we all could support that, but unless you
> think it is detrimental to postgresql for them to include static pgsql
> libs in php (which I do not) it seems we should lobby for them to put in
> postgresql libs over anything else.

And have the same issue where if you install mod_auth_pgsql in apache you
get a crash prone server with two different libs?  no thanks.  the whole
idea of shared objects is that you use the version the sysadmin installed
on the box, not what your package came with.  If I wanted to have umpteen
different unshared-shared libs (i.e. dll hell) crashing my aps randomly,
I'd be running windows.



pgsql-advocacy by date:

Previous
From: Josh Berkus
Date:
Subject: Re: Fwd: Re: enabling postgresql by default
Next
From: Joe Conway
Date:
Subject: Re: Fwd: Re: enabling postgresql by default