Re: CommandCounterIncrement versus plan caching

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Gregory Stark <stark(at)enterprisedb(dot)com>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: CommandCounterIncrement versus plan caching
Date: 2007-11-30 05:56:10
Message-ID: 24247.1196402170@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Gregory Stark <stark(at)enterprisedb(dot)com> writes:
> Wait, shouldn't it be sufficient to do a CCI only in the "if (!plan)" case?

No. The problem is that if you don't do the CCI then you don't get the
invalidation events that might-or-might-not be pending in the inval
queue. So testing for whether the plan is still valid is meaningless
unless that queue's been flushed.

regards, tom lane

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Simon Riggs 2007-11-30 06:31:33 Release Note Changes
Previous Message Trevor Talbot 2007-11-30 05:51:02 Re: 8.2.3: Server crashes on Windows using Eclipse/Junit