I sure hope it gets more attention than some of the other PHP PostgreSQL
bugs.. I don't mean to trash anyone here but the pg_connect problem has been
around since 4.0.1 and has yet to be addressed. One of our programmers is
taking a look at that one but he's not been able to fix it yet.
*crosses fingers*
Is there anything stupendously broken in PG beta 4? I have it on my devel
server and don't want to have to recompile (right now at least, deadlines
are growing close) unless I stand a large chance of pulling the pin on a
grenade somewhere.
Thanks!!
-Mitch
----- Original Message -----
From: "Larry Rosenman" <[EMAIL PROTECTED]>
To: "Tom Lane" <[EMAIL PROTECTED]>
Cc: "PostgreSQL Hackers List" <[EMAIL PROTECTED]>; "Peter
Eisentraut" <[EMAIL PROTECTED]>; "Bruce Momjian" <[EMAIL PROTECTED]>
Sent: Sunday, February 18, 2001 6:02 PM
Subject: Re: (forw) (forw) Re: PHP 4.0.4pl1 BUILD: BUSTED WITH CURRENT CVS
> * Tom Lane <[EMAIL PROTECTED]> [010218 16:54]:
> > Larry Rosenman <[EMAIL PROTECTED]> writes:
> > > OK, I found it. PHP was including postgres.h (which we no longer
> > > install...., so we were picking up a Feb 7 version).
> > > Changing php's ext/pgsql/php_pgsql.h to #include <postgres_fe.h>
> > > fixes it.
> >
> > Hm. Should php be including either one? I would have been in less
> > hurry to invent a new file if I had thought that client apps were
> > including postgres.h ...
> Updated to not include either postgres.h or postgres_fe.h....
>
> FYI, bug # in PHP's DB is 9328.
>
> LER
>
> >
> > regards, tom lane
> --
> Larry Rosenman http://www.lerctr.org/~ler
> Phone: +1 972-414-9812 E-Mail: [EMAIL PROTECTED]
> US Mail: 1905 Steamboat Springs Drive, Garland, TX 75044-6749
>
