Re: Persistent connections in PHP

From: Torsten Zühlsdorff <thorny(at)meisterderspiele(dot)de>
To: pgsql-general(at)postgresql(dot)org
Subject: Re: Persistent connections in PHP
Date: 2007-08-15 10:28:50
Message-ID: f9ukd9$5v1$1@registered.motzarella.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

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 TSearch get it from there? And even if it does, it
> will still held its own copy?

In this case I misunderstood you. I believed, that you get a dictionary
from pg and use it. -.-
Because often people load a dictionary from db to get the translation of
$content, shared memory can make this very fast. My advise based on this
assumption.

Greetings,
Torsten

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Ivan Zolotukhin 2007-08-15 11:41:30 Best practice for: ERROR: invalid byte sequence for encoding "UTF8"
Previous Message Pavel Stehule 2007-08-15 09:57:50 is this trigger safe and efective? - locking (caching via triiggers)