Re: GSoC Proposal - Caching query results in pgpool-II

From: Magnus Hagander <magnus(at)hagander(dot)net>
To: Tatsuo Ishii <ishii(at)postgresql(dot)org>
Cc: m(dot)yamazaki23(at)gmail(dot)com, pgsql-hackers(at)postgresql(dot)org
Subject: Re: GSoC Proposal - Caching query results in pgpool-II
Date: 2011-04-07 08:57:18
Message-ID: BANLkTim-TUjuDsMivACFYJmiwmD5ZQ3pBA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

2011/4/7 Tatsuo Ishii <ishii(at)postgresql(dot)org>:
> In my understanding pqc is not designed to be working with pgpool.
> Thus if a user want to use both query cache and query dispatching,
> replication or failover etc. which are provided by pgpool, it seems
> it's not possible. For this purpose maybe user could *cascade* pqc and
> pgpool, but I'm not sure. Even if it's possible, it will bring huge
> performance penalty.
>
> Another point is cache invalidation. Masanori's proposal includes
> cache invalidation technique by looking at write queries, which is
> lacking in pqc in my understanding.

Probably. My question wasn't necessarily "hasn't this already been
done in pqc", more "should this perhaps build on or integrate with pgc
in order not to duplicate effort". I think at the very least, any
overlap should be researched and identified - because if it can
integrate parts of pgc, or work with, more effort can be spent on the
new parts rather than redoing something that's already been done.

--
 Magnus Hagander
 Me: http://www.hagander.net/
 Work: http://www.redpill-linpro.com/

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Andrew Dunstan 2011-04-07 10:33:08 Re: superusers are members of all roles?
Previous Message Dave Page 2011-04-07 08:26:34 Re: Windows build issues