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

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: (view raw, whole thread or download thread mbox)
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

pgsql-hackers by date

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

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