RE: Install with Apache/PHP (Was "Stubborn Multibyte") - Mailing list pgsql-general

I gave up on 7.1.1 for now, although that is not ideal.  I looked around the
web some more, and saw a recommendation to someone who was using RPMs for
postgresql and had the same problem, saying to install the postgresql-devel
RPM as well.  I don't know how to do that with compiled source, but I then
realized that my successful installs have always been after a full set of
7.0.2 RPMs were already installed.  I tried a 7.1.1 RPM I found on
rpmfind.net, but it complained that it needed about 30 files I did not have.
So I just loaded the same old 7.0.2 RPMs I used before, and it all seems to
work (haven't made the database yet or tried to connect to the web serv.
Why I can't do it with compiled source, why my other machine complained of
disabled multibyte, and whether I will run into any of the bugs fixed in
7.1.1 will remain mysteries.

Now I have one more brand new thing I am seeing.  When I run psql or
createdb, I get a bunch of extra stuff on the screen at startup, \q time,
and any non-help command (including everything little thing it does to
process my request - a \d on an empty db gives me two full screenfuls of sql
and other stuff before saying "no relations").  It's like I have some
super-verbose switch turned on somewhere.  On startup, the first one is:
   010523.20:30:28.625 [14996] read_pg_options: verbose=2,query=2,syslog=0
...which I thought was a clue (the verbose level), but looking at my other
working installation, the pg_options file has the exact same parameters,
including verbose=2, and it doesn't spew all that stuff at me.  Any clues?

--------------------------------
Karen Ellrick
S & C Technology, Inc.
1-21-35 Kusatsu-shinmachi
Hiroshima  733-0834  Japan
(from U.S. 011-81, from Japan 0) 82-293-2838
--------------------------------

> -----Original Message-----
> From: pgsql-general-owner@postgresql.org
> [mailto:pgsql-general-owner@postgresql.org]On Behalf Of Einar Karttunen
> Sent: Wednesday, May 23, 2001 7:19 PM
> To: Karen Ellrick
> Cc: pgsql-general@postgresql.org
> Subject: Re: [GENERAL] Install with Apache/PHP (Was "Stubborn Multibyte")
>
>
> On Wed, 23 May 2001, Karen Ellrick wrote:
>
>
> > during PHP's make:
> >    In file included from pgsql.c:29:
> >    php_pgsql.h:32: postgres.h: No such file or directory
> >
> > Anyone done this before, and had this message?  I am using the
> same tarballs
> > for PHP and Apache that I used on the previous two
> installations.  After it
> > failed the first time, I even tried untarring the previously
> used tarball
> > for postgresql (7.0.2) and pointing to it during configure, but the same
> > error appeared.  There are no shortage of files called postgres.h on the
> > machine, but I don't know where it is looking, and I don't
> think I should
> > have to start disecting the Makefile.  It worked before, so it
> shouldn't be
> > a typo or incompatibility, should it?
> >
> I think a quick solution would be to include the directory where
> postgres.h resides to path. It is by no means an answer to the problem but
> should help if you just need things to work.
>
> eg. export PATH=/usr/local/postgres/include:$PATH
>     replace /usr/local/postgres/include with the path to postgres.h
>
> - Einar Karttunen
>
>
> ---------------------------(end of broadcast)---------------------------
> TIP 4: Don't 'kill -9' the postmaster