On Wed, 2006-09-20 at 14:08 -0400, Tom Lane wrote: > David Fetter <david@xxxxxxxxxx> writes: > > What would be involved in making INSERT/UPDATE/DELETE ... RETURNING be > > on the same level as other table-like things such as VALUES (...), > > ..., (...)? > > Getting rid of their side-effects, which of course ain't happening. > > The problem is the surrounding query might try to execute the command > multiple times ... or not at all ... and what would you like that to > mean? > Wouldn't that be the same as a volatile set-returning function? As I understand it, 8.2 introduced a feature to prevent a volatile function from being executed more times than it is listed in the query. Regards, Jeff Davis
