Re: WIP patch for plan invalidation - Mailing list pgsql-patches

From Tom Lane
Subject Re: WIP patch for plan invalidation
Date
Msg-id 13324.1173580474@sss.pgh.pa.us
Whole thread Raw
In response to Re: WIP patch for plan invalidation  (Gregory Stark <stark@enterprisedb.com>)
List pgsql-patches
Gregory Stark <stark@enterprisedb.com> writes:
> "Tom Lane" <tgl@sss.pgh.pa.us> writes:
>> Comments?

> Why do CREATE/DROP/REINDEX DATABASE no longer call PreventTransactionChain?

I moved those calls into ProcessUtility to avoid having to pass an extra
argument to those functions.  You could call this either way, but there
was already precedent for doing PreventTransactionChain in
ProcessUtility --- several existing commands did it that way.  In the
patch as it stands, ProcessUtility does it for every command in which
the call is unconditional, and we only pass isTopLevel to command
subroutines that have some condition or other affecting what to do.
You could make about an equally good case for pushing all those
PreventTransactionChain calls out to the subroutines, but it didn't
really seem any prettier to do it that way.

            regards, tom lane

pgsql-patches by date:

Previous
From: Gregory Stark
Date:
Subject: Re: WIP patch for plan invalidation
Next
From: Michael Fuhr
Date:
Subject: Fix race condition in size functions