pg.ddx.io  pgsql-php@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: GH <grasshacker@over-yonder.net>
To: Mitch Vincent <mitch@venux.net>
Cc: pgsql-php@postgresql.org
Subject: Re: Crazy PHP-> PostgreSQL errors
Date: Mon, 5 Feb 2001 16:11:37 -0600
Message-ID: <20010205161137.B38912@over-yonder.net> (raw)
In-Reply-To: <014c01c08f9d$bdefca20$0200000a@windows>
References: <4.3.2.7.2.20010205084023.036ddee8@rccd.cc.ca.us>
	<4.3.2.7.2.20010205094402.036d8ea0@rccd.cc.ca.us>
	<014c01c08f9d$bdefca20$0200000a@windows>

On Mon, Feb 05, 2001 at 01:02:02PM -0500, some SMTP stream spewed forth: 
> Warning: 11 is not a valid PostgreSQL result resource in
> /usr/site/php/classes/db_pgsql.inc on line 62
> 
> Ok, this is a bit nasty.. All of the sudden I'm getting all kinds of the
> above errors in my PHP code (code that's worked forever).. It happens on
> both PG 7.0.2, 7.0.3 and 7.1 Beta 4 with both Apache 1.3.14 and 1.3.17..
> 
> It recently started happening on one of our production servers when it was
> taken to PHP 4.0.4pl1 from 4.0.3. I'm not positive where it started
> happening with my development server as the application effected hasn't been
> worked on for a while..
> 
> Between my development server and our effected production server we're using
> two totally different PgSQL classes for database access and both have been
> stable for a long, long time so I'm pretty sure it's not out PHP code...
> 
> It doesn't appear that the backend is crashing.. I get no message that it
> exited abnormally, I swear it's like I'm calling pg_close() somewhere (but
> I'm not)..

Are you using persistent connections?
Are the config files essentially the same (relating to PostgreSQL, of
course)?

> 
> I'm at a loss as to how to debug this, it _appears_ to be PHP 4.0.4pl1
> that's doing something crazy but I'll be damned if I can see what it is..

Would it be possible for you to send perhaps an example of what is
causing the error (i.e. test case)?

We just switched from 4.0.3 to 4.0.4pl1, but not on our production
machines, and I have seen no such behavior (using non-persistent
connections).


Good luck!

gh

> Before it was limited to my development server but after going to PHP
> 4.0.4pl1 on a production server this started to show up everywhere..
> 
> Any ideas/comments/insights would be appreciated!
> 
> -Mitch



view thread (2+ messages)

Message-ID: <20010205161137.B38912@over-yonder.net>
Permalink:  ../20010205161137.B38912@over-yonder.net/
Also on:    postgresql.org/message-id/20010205161137.B38912@over-yonder.net

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients from your mail client; the link fills in
  the headers below: reply via email
  Some clients, webmail especially, drop In-Reply-To and References from
  a link, and the reply then starts a new thread: use the mbox below.

  To: pgsql-php@postgresql.org
  Cc: grasshacker@over-yonder.net, mitch@venux.net
  Subject: Re: Crazy PHP-> PostgreSQL errors
  In-Reply-To: <20010205161137.B38912@over-yonder.net>
  References: <4.3.2.7.2.20010205084023.036ddee8@rccd.cc.ca.us> <4.3.2.7.2.20010205094402.036d8ea0@rccd.cc.ca.us> <014c01c08f9d$bdefca20$0200000a@windows> <20010205161137.B38912@over-yonder.net>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox