Gregory Stark <[EMAIL PROTECTED]> writes:
> "Tom Lane" <[EMAIL PROTECTED]> 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
"Gregory Stark" <[EMAIL PROTECTED]> writes:
> "Tom Lane" <[EMAIL PROTECTED]> writes:
>
>> Comments?
>
> Why do CREATE/DROP/REINDEX DATABASE no longer call PreventTransactionChain?
sigh, nevermind.
--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com
--
"Tom Lane" <[EMAIL PROTECTED]> writes:
> Comments?
Why do CREATE/DROP/REINDEX DATABASE no longer call PreventTransactionChain?
--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com
---(end of broadcast)---
TIP 5: don't forget to
This is what I've done so far on the plan-invalidation project. This
creates a plan cache manager module and restructures things enough for
prepared statements to use it (both those generated at the SQL level
by PREPARE, and those coming from extended query protocol messages).
I haven't yet done a