Re: Effects of GUC settings on automatic replans - Mailing list pgsql-hackers

From Jan Wieck
Subject Re: Effects of GUC settings on automatic replans
Date
Msg-id 4601789A.6030809@Yahoo.com
Whole thread Raw
In response to Re: Effects of GUC settings on automatic replans  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
On 3/21/2007 1:46 PM, Tom Lane wrote:
> Jan Wieck <JanWieck@Yahoo.com> writes:
>> On 3/20/2007 1:11 PM, Tom Lane wrote:
>>> search_path
>>> add_missing_from
>>> transform_null_equals
>>> sql_inheritance
> 
>> Don't we actually store the parsetree in the query cache, and doesn't 
>> that actually make a lot of the above rather NOT affect the resulting 
>> plan any more?
> 
> No, what the code now does is to store the raw grammar output --- a
> replan includes a fresh pass through parse_analyze.  This must happen
> if we want the thing to cope with dropping and replacing temp tables,
> which is one of the main use-cases ...

Ah, yes, that makes more cents now.


Jan

-- 
#======================================================================#
# It's easier to get forgiveness for being wrong than for being right. #
# Let's break this rule - forgive me.                                  #
#================================================== JanWieck@Yahoo.com #


pgsql-hackers by date:

Previous
From: Bruce Momjian
Date:
Subject: Re: CREATE INDEX and HOT - revised design
Next
From: Bruce Momjian
Date:
Subject: Re: CREATE INDEX and HOT - revised design