[imp] Still Postgres Persistent Conections problems

[Brent J. Nordquist]

On Wed, 14 Mar 2001, Alexander E. Belck <alexb@iol.psi.br> wrote:

> So far I understood, all pg_pconnect where replaced by pg_connect in version
> 2.2.4 and I wonder why there is still a pg_pconnect in
> .../horde/imp/lib/db.pgsql.

Rich fixed this after 2.2.4 release:

----------------------------
revision 1.1.2.4
date: 2001/02/04 03:46:59;  author: rich;  state: Exp;  lines: +1 -1
Changed this weeks ago on our production system to no ill effect, may
as well make it consistent with horde/phplib/db_pgsql.inc by using
pg_connect instead of pg_pconnect.
----------------------------

(1.1.2.4 does just like you did; change pg_pconnect to pg_connect on that
one line.)

> The errors that this change causes follows (I copyed them after trying to
> login with db.pgsql changed to use pg_connect):
>
> Warning: 1 is not a valid PostgreSQL link resource in
> /usr/local/apache/php/db_pgsql.inc on line 52

Sorry I don't have anything to suggest for this one; I don't know very
much about PostgreSQL as we're not yet using it in production here.
Hopefully someone else will have a suggestion.

> I don't use the default 32 backends of Postgres and I got the problem with
> just a single user.
>
> -----Mensagem original-----
> De: Rich Lafferty [mailto:rich@bofh.concordia.ca]Em nome de Rich
> Lafferty
> Enviada em: quinta-feira, 1 de março de 2001 23:06
> Para: imp@lists.horde.org
> Assunto: Re: [imp] Postgres and Persistent Conections
>
> *What* errors? Changing all occurrences of 'pg_pconnect' to
> 'pg_connect' is not only okay, but has already been done in cvs. We
> use it here on a machine that gets up to two thousand logins a day
> with no problems at all.
>
> I suspect the errors are related to something else (like, say, running
> out of postgres connections -- you're not using the default of 32
> backends/32 buffers, are you?)

-- 
Brent J. Nordquist <bjn@horde.org>
Yahoo!: Brent_Nordquist / AIM: BrentJNordquist / ICQ: 76158942