Skip site navigation (1) Skip section navigation (2)

Re: invalidating cached plans

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: "Qingqing Zhou" <zhouqq(at)cs(dot)toronto(dot)edu>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: invalidating cached plans
Date: 2005-04-02 16:44:39
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-hackers
"Qingqing Zhou" <zhouqq(at)cs(dot)toronto(dot)edu> writes:
> "Neil Conway" <neilc(at)samurai(dot)com> writes
>> PostgreSQL should invalidate a cached query plan when one of the objects
>> the plan depends upon is modified.

> It just comes into my mind that current cache invalidation implementation
> may need to consider the future query result cache.

There isn't likely ever to be a query result cache.  The idea has been
proposed before and rejected before: too much complexity and overhead
for too little prospective gain.  If you need such a thing it makes
more sense to do it on the application side and save a network round

			regards, tom lane

In response to

pgsql-hackers by date

Next:From: Joshua D. DrakeDate: 2005-04-02 16:51:19
Subject: Re: [GENERAL] plPHP in core?
Previous:From: Greg StarkDate: 2005-04-02 16:27:26
Subject: Re: Debugging deadlocks

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group