Ah yes - that was me making an unfortunate exptrapolation without thinking
it through.
Of course, PHP implements persistent connections for you, etc., etc., not
the postgres client library.
Chris
> -----Original Message-----
> From: Neil Conway [mailto:nconway@klamath.dyndns.org]
> Sent: Tuesday, 30 July 2002 12:11 AM
> To: Christopher Kings-Lynne
> Cc: Luis Alberto Amigo Navarro; pgsql-hackers@postgresql.org
> Subject: Re: [HACKERS] question on backends
>
>
> On Mon, Jul 29, 2002 at 11:28:54PM +0800, Christopher Kings-Lynne wrote:
> > libpq has a function pconnect as opposed to connect that will do it.
>
> libpq has neither function, AFAIK.
>
> As for persistent backends, it's on the TODO list, but I'm not aware
> that anyone has put any work into implementing it. At the moment,
> a backend connects to a single database for its entire lifecycle -- so
> you'd either need one pool of persistent backends for each database
> in use, or you'd need to allow a backend to change the database it is
> connected to.
>
> Cheers,
>
> Neil
>
> --
> Neil Conway <neilconway@rogers.com>
> PGP Key ID: DB3C29FC
>
