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: 4396.1112460279@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
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
trip.

regards, tom lane

In response to

Browse pgsql-hackers by date

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