From: Tom Lane <tgl@sss.pgh.pa.us>
To: Tom Samplonius <tom@sdf.com>
Cc: mlw <markw@mohawksoft.com>
Cc: PostgreSQL-development <pgsql-hackers@postgresql.org>
Cc: PostgreSQL-interfaces <pgsql-interfaces@postgresql.org>
Subject: Re: [INTERFACES] Re: PHP and PostgreSQL
Date: Wed, 03 Jan 2001 01:07:16 -0500
Message-ID: <15332.978502036@sss.pgh.pa.us> (raw)
In-Reply-To: <Pine.BSF.4.05.10101022030040.8582-100000@misery.sdf.com>
References: <Pine.BSF.4.05.10101022030040.8582-100000@misery.sdf.com>
Tom Samplonius <tom@sdf.com> writes:
> ... Besides, as already has been tested, session startup time is
> minimal.
Well, mumble ...
I think the startup time is negligible if you are issuing a reasonable
number of queries per session (say a few dozen). But if you connect,
issue one query, and disconnect, then undoubtedly you will find that
performance sucks.
We could probably do more to improve this situation on the server side,
but IMHO it makes most sense to address the issue on the client side
via connection reuse. The main reason for this is that a significant
amount of the startup time for a standard connection consists of
authentication overhead and context setup overhead (such as setting the
timezone and character set encoding that the client wants to use).
A general-purpose connection-reuse facility on the server end cannot
eliminate these overheads, whereas it's trivial to avoid them within
the context of a multi-threaded client.
Bottom line: better to solve it by fixing Apache or PHP.
regards, tom lane
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 using the --to and --cc options:
reply via email
To: pgsql-interfaces@postgresql.org
Cc: tgl@sss.pgh.pa.us, tom@sdf.com, markw@mohawksoft.com, pgsql-hackers@postgresql.org
Subject: Re: [INTERFACES] Re: PHP and PostgreSQL
In-Reply-To: <15332.978502036@sss.pgh.pa.us>
* 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