On 07/04/2011 23:02, Rich Shepard wrote:
On Thu, 7 Apr 2011, Raymond O'Donnell wrote:
Have you located the Postgres log yet? ISTM that that's where you need to
be looking.
Ray,
Yes ... and no. I think that I turned on all the right switches in
postgresql.conf, but the logging is displayed to stdout rather than to
syslog. I have a /var/log/postgresql but that has a few entries from last
December and nothing since. I can post the .conf file to learn what I set
incorrectly (or didn't set when it should be).
Hi Rich,
That is a bit odd. Yes, please do post the relevant bits of the .conf -
clearer heads than mine may spot something.
What platform are you on (maybe you said already, and I missed it)? How
did you install PostgreSQL?
In C and python I'd be putting little stub code to print in the function
with the problems so I can tell just where I am when it fails. I've no idea
of how to do this in php, or where it would be appropriate to insert
code to
generate diagnostics.
I think you've already got all the diagnostics you're going to get from
the PHP side of things... there are PHP functions to get the most recent
error from the Postgres connection, but it sounds as though the
connection isn't getting made in the first place (which of course
negates my upthread guess about bytea... doh).
Ray.
--
Raymond O'Donnell :: Galway :: Ireland
rod@xxxxxx