Re: Dead code as a result of plan cache invalidation? - Mailing list pgsql-hackers

From Gregory Stark
Subject Re: Dead code as a result of plan cache invalidation?
Date
Msg-id 871wfocd0k.fsf@oxford.xeocode.com
Whole thread Raw
In response to Re: Dead code as a result of plan cache invalidation?  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Dead code as a result of plan cache invalidation?  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
"Tom Lane" <tgl@sss.pgh.pa.us> writes:

> Gregory Stark <stark@enterprisedb.com> writes:
>> Should this case at heaptuple.c:1606 be turned into an elog() now that we have
>> plan cache invalidation?
>
> No, I think it's good as-is.  Reading the column as null is the correct
> behavior.

Isn't the correct behaviour that you would have been prevented from executing
that plan and forced to replan your query?

Let me put it another way, how would I write a test case to cover these lines
of code and not receive an error from replanning?

--  Gregory Stark EnterpriseDB          http://www.enterprisedb.com



pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Dead code as a result of plan cache invalidation?
Next
From: Bruce Momjian
Date:
Subject: Re: what is difference between LOCAL and GLOBAL TEMP TABLES in PostgreSQL