Re: Subquery WHERE IN or WHERE EXISTS faster?

Поиск
Список
Период
Сортировка
От Rusty Conover
Тема Re: Subquery WHERE IN or WHERE EXISTS faster?
Дата
Msg-id B68AFD89-4213-4912-8108-8C41913F45CB@infogears.com
обсуждение исходный текст
Ответ на Re: Subquery WHERE IN or WHERE EXISTS faster?  (Ulrich <ulrich.mierendorff@gmx.net>)
Ответы Re: Subquery WHERE IN or WHERE EXISTS faster?
Список pgsql-performance
On Jun 30, 2008, at 1:29 AM, Ulrich wrote:

> I think it will be fast, because the "IN set", which is the result
> of "SELECT processorid FROM users_processors WHERE userid=4040", is
> limited to a maximum of ~500 processors which is not very big.
> Increasing Postgres' RAM would be difficult for me, because I am
> only running a very small server with 256MB RAM and the webserver
> also likes to use some RAM.
>
> Does Postgre cache the HASH-Table for later use? For example when
> the user reloads the website.
>

No the hash table only lives as long as the query is being executed.
If you're looking for generic caching, I'd suggest memcached may be
able to fill your needs.

Cheers,

Rusty
--
Rusty Conover
InfoGears Inc.
http://www.infogears.com







В списке pgsql-performance по дате отправления:

Предыдущее
От: Ulrich
Дата:
Сообщение: Re: Subquery WHERE IN or WHERE EXISTS faster?
Следующее
От: Matthew Wakeling
Дата:
Сообщение: Re: Planner should use index on a LIKE 'foo%' query