Re: wCTE: why not finish sub-updates at the end, not the beginning? - Mailing list pgsql-hackers

From Heikki Linnakangas
Subject Re: wCTE: why not finish sub-updates at the end, not the beginning?
Date
Msg-id 4D68B78B.6050905@enterprisedb.com
Whole thread Raw
In response to Re: wCTE: why not finish sub-updates at the end, not the beginning?  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: wCTE: why not finish sub-updates at the end, not the beginning?
List pgsql-hackers
On 26.02.2011 07:55, Tom Lane wrote:
> So we really need some refactoring here.  I dislike adding another
> fundamental step to the ExecutorStart/ExecutorRun/ExecutorEnd sequence,
> but there may not be a better way.

Could you keep the sequence unchanged for non-EXPLAIN callers with some 
refactoring? Add an exposed function like ExecutorFinishRun() that 
Explain calls explicitly in the EXPLAIN ANALYZE case, and modify 
ExecutorEnd to call it too, if it hasn't been called yet and the 
explain-only flag isn't set.

--   Heikki Linnakangas  EnterpriseDB   http://www.enterprisedb.com


pgsql-hackers by date:

Previous
From: Bruce Momjian
Date:
Subject: Re: Keywords in pg_hba.conf should be field-specific
Next
From: Jan Urbański
Date:
Subject: Re: pl/python tracebacks