From: | Jan Wieck <JanWieck(at)Yahoo(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: Effects of GUC settings on automatic replans |
Date: | 2007-03-21 18:25:30 |
Message-ID: | 4601789A.6030809@Yahoo.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 3/21/2007 1:46 PM, Tom Lane wrote:
> Jan Wieck <JanWieck(at)Yahoo(dot)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(at)Yahoo(dot)com #
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 2007-03-21 18:36:25 | Re: CREATE INDEX and HOT - revised design |
Previous Message | Bruce Momjian | 2007-03-21 18:24:26 | Re: CREATE INDEX and HOT - revised design |