Greetings All,
I have to authenticate against an existing (constantly modified) PostgreSQL
database under Solaris 10 (X86). While my PHP scripts are an obvious
no-brainer, the rest of the contents need to be protected as well (images,
etc) so the http authentication is required. I am using the blastwave
Apache2 and PostgreSQL packages.
I am concerned about slowing down apache too much with these postgres
queries on every get and post - and I would love to have some tips from you
guys on how to avoid that (beyond the normal tuning for postgres). For now,
I can not even get it working at all so I can test it. I have posted on
blastwave and solaris groups without reply but I have been watching this
list for years and you guys always come through if you can.
When I enable mod_dbd and set up the directory access, apache complains that
it can not find the DBDriver pgsql and I read from the manual page that it
is looking for apr_dbd_pgsql.so to be available to apache. Other research
indicates libpq.so is what it is looking for. Yet other research says that
libaprutil-1.so should contain one of these two when you look at it in a ldd
command. The closest thing that my system seems to have is the libpq.so in
the /opt/csw/postgres/lib directory and even when I provide a symbolic link
from the /opt/csw/apache2/lib for this library I still get a not found
condition from the DBDriver setting. It seems Google only helps if you are
not on Solaris - and even then not so much.
Is ANYONE using blastwave packages and getting the http authentication to
work against a PostgreSQL database on Solaris 10? If so, how? I am out of
straws to grasp.
As I say, from a performance point of view, I would really like to know if
there is anything I can do to make sure that postgres is performing as
quickly as possible under apache2 so that my http authentication is not
impacted too significantly.
Thanks in advance for any help that anyone can be!
Jeff Brower