Hannes Dorbath schrieb:
On 15.08.2007 10:53, Torsten Zühlsdorff wrote:
If the dictionary is not too large, you should store it directly in
the memory of the server. Therefore you can use Shared Memory
(http://www.php.net/shmop, http://de3.php.net/manual/en/ref.sem.php).
Uhm, but how does TSea
Hannes Dorbath schrieb:
On 14.08.2007 23:13, Dmitry Koterov wrote:
Pconnects are absolutely necessary if we use tsearch2, because it
initializes its dictionaries on a first query in a session. It's a very
heavy process (500 ms and more). So, if we do not use pconnect, we waste
about 500 ms on ea
On 15.08.2007 10:53, Torsten Zühlsdorff wrote:
If the dictionary is not too large, you should store it directly in the
memory of the server. Therefore you can use Shared Memory
(http://www.php.net/shmop, http://de3.php.net/manual/en/ref.sem.php).
Uhm, but how does TSearch get it from there? An
On 14.08.2007 23:13, Dmitry Koterov wrote:
Pconnects are absolutely necessary if we use tsearch2, because it
initializes its dictionaries on a first query in a session. It's a very
heavy process (500 ms and more). So, if we do not use pconnect, we waste
about 500 ms on each DB connection. Too muc
Pconnects are absolutely necessary if we use tsearch2, because it
initializes its dictionaries on a first query in a session. It's a very
heavy process (500 ms and more). So, if we do not use pconnect, we waste
about 500 ms on each DB connection. Too much pain.
Or, of course, pconnect may be repla
On Mon, 13 Aug 2007 11:30:37 -0500
"Scott Marlowe" <[EMAIL PROTECTED]> wrote:
> Oh, one other thing that contributes to the problem
Thanks for the replies - all of this was very useful info.
Josh
---(end of broadcast)---
TIP 2: Don't 'kill -
> 6: The reason for connection pooling is primarily to twofold. One is
> to allow very fast connections to your database when doing lots of
> small things where connection time will cost too much. The other is
> to prevent your database from having lots of stale / idle connections
> that cause i
On 8/13/07, Scott Marlowe <[EMAIL PROTECTED]> wrote:
> On 8/13/07, Josh Trutwin <[EMAIL PROTECTED]> wrote:
> > On Mon, 13 Aug 2007 09:44:26 -0500
> > Erik Jones <[EMAIL PROTECTED]> wrote:
> >
> > > I'll agree with Scott on this one. (Not that I can recall
> > > specifically ever disagreeing with h
On 8/13/07, Josh Trutwin <[EMAIL PROTECTED]> wrote:
> On Mon, 13 Aug 2007 09:44:26 -0500
> Erik Jones <[EMAIL PROTECTED]> wrote:
>
> > I'll agree with Scott on this one. (Not that I can recall
> > specifically ever disagreeing with him before...). Unless you
> > know all of the potential caveats
Le lundi 13 août 2007, Erik Jones a écrit :
> If you need something to pool connections, look at pgpool.
Or better yet, pgbouncer. At least for my values of better :)
https://developer.skype.com/SkypeGarage/DbProjects/PgBouncer
http://pgfoundry.org/projects/pgbouncer/
Hope this helps,
--
dim
On Mon, 13 Aug 2007 09:44:26 -0500
Erik Jones <[EMAIL PROTECTED]> wrote:
> I'll agree with Scott on this one. (Not that I can recall
> specifically ever disagreeing with him before...). Unless you
> know all of the potential caveats associated with php's persisent
> postgres connections and ha
On Aug 13, 2007, at 9:35 AM, Scott Marlowe wrote:
On 8/13/07, Naz Gassiep <[EMAIL PROTECTED]> wrote:
Hi,
Does the connection pooling feature of PHP cause the persistent
connections to keep the properties between accesses? E.g., if a user
takes a connection, sets a timezone to it using SET
On 8/13/07, Naz Gassiep <[EMAIL PROTECTED]> wrote:
> Hi,
> Does the connection pooling feature of PHP cause the persistent
> connections to keep the properties between accesses? E.g., if a user
> takes a connection, sets a timezone to it using SET TIMEZONE, will the
> next user who happens to t
2007/8/13, Naz Gassiep <[EMAIL PROTECTED]>:
> Hi,
> Does the connection pooling feature of PHP cause the persistent
> connections to keep the properties between accesses? E.g., if a user
> takes a connection, sets a timezone to it using SET TIMEZONE, will the
> next user who happens to take thi
Hi,
Does the connection pooling feature of PHP cause the persistent
connections to keep the properties between accesses? E.g., if a user
takes a connection, sets a timezone to it using SET TIMEZONE, will the
next user who happens to take this connection get it in that same state,
or will it
Has anyone played around with the new PHP ODO drivers and been able to
successfully set up an object using persistent connections? I tried to
follow the documentation in the PHP manual to send an array in the PDO
constructor but receive a warning message that the underlying driver
does not supp
16 matches
Mail list logo
